OPENCOVEN · PERSISTENT AI FAMILIARS
Where AI Meets
Continuity.
Named familiars with memory, tools, identity, and continuity — running locally, inside your projects, on your terms.
Why Coven
AI that can stay
Familiars keep a name, role, memory, and place in the work across every session.
Local runtime substrate
Coven keeps execution bounded to explicit projects and tools. Not a harness — the layer beneath.
Shared ecosystem
Codex, Claude Code, CastCodes, dashboards, and docs built to fit together.
Owned by builders
Open framework, inspectable architecture, practical extension points — yours to modify.
Architecture
One neutral layer between the harness and your code.
Coven sits between every supported agent CLI and the project you're actually working in. Commands flow down, output and memory flow up, and every boundary is explicit.
pick a node
How Coven fits into your stack
Pick any node to inspect how it fits into the runtime.
- Commands flow down: harness → runtime → your project
- Output, state, and memory flow back up the return path
- Every boundary is enforced at runtime, not just drawn here
How It Works
Pick a layer. See what it actually does.
Memory, sessions, harnesses, and tools are the four moving parts. Each tab is a working preview of how that piece behaves in a real Coven session.
Memory
Continuity that survives the chat window.
Project context, decisions, and preferences accumulate per familiar across sessions. Step through the timeline on the right to see how a familiar's working memory grows from one session to the next.
Sessions
Project-scoped, lifecycle-aware, replayable.
Each harness run is a session record bound to a directory and a familiar. Filter the list on the right to see how Coven tracks running, idle, and archived work — all visible, never abandoned.
Harnesses
One adapter contract. Many agent CLIs.
Codex, Claude Code, and any future harness plug in through the same neutral interface. Click a harness on the right to see how it shows up inside the runtime.
Tools
Every tool call passes through an inspectable gate.
The tool gateway mediates filesystem, git, shell, and web access. Pick a tool category to see the contract Coven enforces before that tool ever runs.
Compare
Why Coven, not just a harness?
Same agent CLIs, different runtime around them. Pick a row to see how each option actually behaves.
| Capability | Raw harness Claude Code, Codex direct | Other tools IDE-bound agents, suites | Best fit Coven recommended runtime |
|---|---|---|---|
| ✗ | − | ✓ | |
| − | − | ✓ | |
| ✗ | − | ✓ | |
| − | − | ✓ | |
| ✗ | − | ✓ | |
| ✓ | ✗ | ✓ |
Cross-session memory
Raw harnesses lose state when the chat ends; most other tools save chat history but not curated working memory per familiar. Coven stores explicit notes that persist and surface in the next session.
Quick Start
Run your first familiar in three commands.
Coven runs locally inside the projects you already have. Verify, start, and resume — memory persists across every session.
01 · Verify
npx @opencoven/cli doctor Checks your environment and detects supported harnesses — Codex, Claude Code, and more.
02 · Start a session
coven run claude "fix the failing tests" Launches a project-scoped session through Coven's managed PTY, bound to the current working directory.
03 · Resume anywhere
coven sessions Interactive browser to rejoin, summon, archive, or view logs — work picks up where you left off.
Ecosystem
Living Workspace of Familiar Agents
OpenCoven turns AI from a blank chatbox into a durable workspace: familiars with memory and tools, local runtime control, open dashboards, desktop surfaces, and an ecosystem builders can inspect, customize, and own.