Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,10 @@ More screenshots and demos: [gallery](gallery.md).
## Why construct?

- **tmux for agent fleets** — manage Codex, Claude Code, OpenCode, Muse,
Antigravity, Grok, and smith sessions from your terminal — or let an agent
coordinate them.
SSH-friendly, single Rust binary.
Antigravity, Grok, and smith sessions from your terminal. Sessions live in
the daemon, not your terminal: SSH drops, laptop sleeps — agents keep
working, and you reattach exactly where you left off, scrollback and all.
Single Rust binary.
- **Lineage** — sessions branch like ideas do: fork one when you want a
parallel attempt (new idea, side quest, or a long shot) — even a
cross-harness fork — and merge the results back.
Expand All @@ -38,7 +39,9 @@ More screenshots and demos: [gallery](gallery.md).
<img src="https://raw.githubusercontent.com/construct-worlds/construct/90d02bd2c1e6108eaa5c763bde9e2d78f8786691/demos/program.gif" alt="construct playbook demo" width="70%">
- **Agent-to-agent orchestration** — let your Codex and Claude Code sessions
talk to each other: one agent can hand a task to another, check how it's
going, and pick up the results.
going, and pick up the results. Every session gets construct's MCP tools,
so any harness can spawn subagents, send them input, and read their output
— no glue code.
- **ACP (Agent Client Protocol) server** — point Agent Client Protocol clients at
`construct acp` to create, load, resume, prompt, cancel, and close construct
daemon sessions through the same installed binary.
Expand Down
Loading