Skip to main content
Alpha developer preview

Build self-evolving agents with Agent Slots.

Demiurge uses Agent Slots to extend capability boundaries and logic design without changing the Host harness. File-backed Agent Cores can compose agents, state, tools, skills, and MCP while evolving under Host control.

Understand Agent SlotsQuick StartRead the Manual

APIs, runtime layout, and authoring contracts may still change while the project is in alpha.

agent slot loop
Inbound
Bootstrap / input slots
Provider + tool loop
Output slots
Slots can compose
toolsskillsMCPstatechild agents
Host governance
approvalsdeliveryrollback

A runtime shaped around evolvable agent boundaries.

Demiurge keeps custom capability and logic design in Agent Core files and packages while the Host owns the risky runtime machinery.

Agent Slots

Slots define where Core-authored behavior enters the loop and which governed effects it may request.

Package-composed capabilities

Packages install slots, tools, skills, libraries, and child cores without adding feature code to the harness.

Host-governed effects

Provider calls, tool dispatch, approvals, state, delivery, promotion, and rollback stay host-owned.

Versionable Core files

Agent Cores stay readable, diffable, testable, promotable, and evolvable as ordinary files.

How Agent Slots Work

Packages attach bootstrap, input, and output behavior through Agent Slots. Custom code can control subagent calls and authored logic while the host keeps provider access, approvals, delivery, promotion, and rollback under control.

Basic Memory System

A memory package adds bootstrap context from local files before the turn runs, without moving memory ownership into the host harness.

Text-to-speech output

A TTS package adds an output slot that renders spoken replies while delivery remains host-owned.

Speech-to-text input

An STT package adds an input slot that turns voice into governed turn context without changing the host loop.

How Slots fit the loop

Tools act. Skills guide. MCP connects. Slots decide where behavior enters the agent loop.

  1. User, channel, or schedule input enters the host runner.
  2. Bootstrap and input slots shape session and turn context.
  3. The provider and tool loop runs under host governance.
  4. Slots can compose tools, MCP, state, skills, or child agents.
  5. Output slots deliver text, media, artifacts, or structured results.
  6. The evolver can propose slot changes; the host gates promotion.

Try it locally

Use the fake provider first to verify the runtime without an API key.

scripts/install.sh
~/.demiurge/demiurge-agent/.venv/bin/demiurge --provider fake