01 · BOUNDARY
Start inside a project root.
Every launch is tied to a real repository path. Cwd, input, process control, and file-sensitive operations stay inside the local boundary Coven validates.
OPENCOVEN · LOCAL AGENT RUNTIME
Controlled multi-agent orchestration.
Coven gives Codex, Claude Code, and future harnesses a shared local room: explicit project boundaries, attachable sessions, durable history, and one authority layer for execution.
HOW IT WORKS
Three states, one substrate.
OpenCoven keeps agent work visible and bounded. The harness may be powerful; the project boundary remains explicit.
02 · SESSION
Run a harness, not a mystery.
Codex, Claude Code, and future adapters run through a neutral PTY contract with session records, titles, events, input, attach, and kill semantics.
03 · COCKPIT
Expose one local API.
comux, OpenMeow, OpenClaw, and purpose-built clients can all read the same session state instead of inventing separate orchestration loops.
HARNESSES
Bring your agents. Keep the room.
Coven does not replace the agent. It gives each agent a controlled execution chamber that the rest of the OpenCoven ecosystem can observe, attach to, and coordinate around.
Launch coding tasks in a project-scoped PTY with visible output and durable session history.
Run Claude Code where it belongs: inside the chosen repo, under Coven-managed lifecycle control.
The runtime shape stays harness-neutral so new agent CLIs can join without rewriting clients.
WHY LOCAL CONTROL
Powerful, not loose.
⌁
Rust authority boundary.
The daemon is the final validator for launch, cwd, input, kill, and path-sensitive requests. Clients can suggest; Coven decides.
◌
Attachable by design.
Sessions are not disposable logs. They can be listed, replayed, followed, and reattached from the CLI or a first-party cockpit.
▣
History that survives.
SQLite-backed metadata and event logs preserve context across daemon restarts without handing your project loop to a cloud queue.