Build file-backed, self-evolving Agent Cores.
English 中文
Website · Docs · Quick Start · Customize a Core · Latest Release
Demiurge is an Alpha-stage agent framework that uses the distinctive Agent Slots model to extend capability boundaries and logic design without changing the Harness. It can also self-iterate inside a Host-controlled environment. A file-backed Agent Core can implement multi-agent collaboration, state management, tool composition, skill composition, MCP composition, and self-evolution under Host control.
Status: alpha / developer preview. Runtime layout, authoring contracts, and
package behavior may still change before 1.0.0.
gituv- Node.js 20 or newer for the TUI
- An OpenAI-compatible provider endpoint and API key when you are ready to use a real model
Managed install is the default user path:
scripts/install.sh
~/.demiurge/demiurge-agent/.venv/bin/demiurge init
~/.demiurge/demiurge-agent/.venv/bin/demiurge --provider fakeSource checkout development uses uv:
uv sync --all-groups
uv run demiurge --provider fakeNormal launches use the tracked packaged TUI bundle even when an ignored
ui-tui/dist/entry.js exists in a source checkout. TUI contributors can opt
into local source artifacts with DEMIURGE_TUI_DEV=1; protocol/build identity
mismatches fail before the operator gateway initializes.
If you want to use a real provider, run demiurge setup to configure your API key and endpoint.
Follow the Quick Start for the full first run, then use Configure a Provider to add a real model profile.
Agent Slots let packages attach bootstrap, input, and output behavior, and let custom code control subagent calls and authored logic, while the host keeps provider access, approvals, delivery, Git revision promotion, and rollback under control.
Basic Memory System
memory-basic-package-demo.mp4
Text-to-speech output
tts-package-demo.mp4
Speech-to-text input
stt-package-demo.mp4
assistant/
├── agent.yaml
└── agent/
├── SOUL.md
├── pipelines.yaml
├── bootstrap/
├── input/
├── output/
├── tools/
├── skills/
├── schedules/
├── mcp/
└── lib/
The runtime initializes ~/.demiurge/.core.git from the source agents/ tree
and checks out the live agents tree at ~/.demiurge/agents. Runtime core edits,
evolve runs, package installs, package uninstalls, promotions, and rollbacks are
Git revisions in that repository. Direct edits under ~/.demiurge/agents are
saved as core revisions before run/edit workflows load the live core. Package
recipes install reusable components into runtime cores without modifying the
source templates or host lock file.
- Demiurge Manual
- Quick Start
- Configure a Provider
- Choose a Workspace
- Troubleshoot
- Write a Package Recipe
- Publish a Package Repository
- Latest Release: 0.8.0
For repository workflow and verification rules, see CONTRIBUTING.md.
Apache-2.0. See LICENSE.