Latest Release

Keep Agents.
Wake Them Later.
Make Work Durable.

Holon is a local-first runtime for agents that should keep working across time, not just answer one prompt and disappear.

Headless by default. Event-driven. Explicit about state, trust, tools, and user-facing delivery.

$ holon run "watch this task"
Loading durable agent state...
Opening tools and workspace context...
Agent entered waiting state:
timer, callback, or operator wake
Recording transcript and task state...
✔ Ready to resume when work arrives
http://127.0.0.1:8787/agents/default/status
$ _

Quickstart

Build the current Rust runtime locally and try the CLI.

# Build from source
git clone https://github.com/holon-run/holon.git
cd holon
cargo build

# Run a one-shot prompt through the runtime
cargo run -- run "Summarize the current workspace"

# Inspect CLI surfaces
cargo run -- --help
cargo run -- agents --help
Status: The Rust runtime is now the main development line. Release packaging and old workflow automation will be rebuilt after this cutover.
# Start the local HTTP runtime
cargo run -- serve

# In another shell, inspect status
curl http://127.0.0.1:8787/runtime/status

# List public agents
curl http://127.0.0.1:8787/agents
Model: Holon keeps runtime state, events, tasks, transcripts, and agent control surfaces explicit so long-lived work remains inspectable.

Why Holon?

Useful agents need more than a chat loop. They need state, wakeups, delegation, and clear delivery boundaries.

🎯

Headless by Default

Run agents from a CLI, daemon, or control surface without binding the runtime to a single UI.

📦

Durable State

Keep transcripts, tasks, events, timers, work items, and runtime status available for later turns.

🔒

Explicit Trust

Preserve provenance for operator input, runtime events, external callbacks, and tool results.

🔄

Wait And Wake

Let agents sleep on timers, callbacks, tasks, or operator input and resume with context intact.

🔌

Provider Model

Keep model providers and tool execution behind runtime contracts instead of a separate SDK bundle.

⚙️

Inspectable Work

Expose agent state, task output, worktree summaries, and user-facing briefs through stable surfaces.

How It Works

Holon separates runtime orchestration from one-off model calls.

01

Ingress

Prompt or event

→
02

State

Load context

→
03

Execute

Tools and tasks

→
04

Wait

Sleep or delegate

→
05

Deliver

Brief or resume

Build agents that can keep working.

Holon makes runtime state explicit.