Coven
A local-first runtime substrate that lets Codex, Claude Code, and GitHub Copilot CLI agent sessions run visibly and safely inside explicit project boundaries.
- Source repo
- OpenCoven/coven
- Stars
- ★ 76
- Last updated
- today
- License
- MIT
- Primary language
- Rust
- FA score
- 66/100 · Some gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude CodeChatGPT (Partial support)
- Cost
- Free, no paid service needed
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- A developer switching between Codex, Claude Code, and GitHub Copilot CLI in one repository wants session history, event logs, and state managed locally by one daemon.
- Not a fit if
- Teams needing a mature, stable 1.0 tool — Coven is an early MVP with documented rough edges
- Users running untrusted prompts in repositories with sensitive secrets, since session logs may capture them
- Users on Alpine Linux or other non-glibc x64 environments
- Website
- opencoven.ai ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-20latest release v0.5.0 (2026-11-10)
- Source review
- 66/100 · Some gaps
What does this agent do, and when should you use it?
Coven is the local harness substrate of the OpenCoven ecosystem, giving coding-agent CLIs like Codex, Claude Code, and GitHub Copilot CLI a shared room for project-scoped work. A Rust daemon is the authority boundary: session launch, cwd validation, PTY execution, event logging, and SQLite persistence all live in the daemon, while the CLI, TUI, and other clients are convenience layers — security decisions flow inward to the daemon, never outward. The architecture is local-first: state is persisted on-machine in SQLite and exposed via a same-user local IPC API defined by the coven.daemon.v1 contract. It ships as the npm package @opencoven/cli with support for macOS, Linux x64 (glibc), and Windows x64. It is an MIT-licensed early MVP in active development, with canonical documentation at docs.opencoven.ai.
Coven's concrete operations center on project-scoped agent sessions: coven setup codex completes the provider-owned login, coven doctor checks local readiness, and coven daemon start launches the Rust daemon that handles cwd validation, PTY lifecycle, event logging, and SQLite persistence. coven run codex "fix the failing tests" launches a Codex session inside the project boundary; coven sessions browses and manages session history; coven daemon stop halts the daemon. Supported harnesses are Codex, Claude Code, and GitHub Copilot CLI, with an adapter contract (docs/HARNESS-ADAPTERS.md) for future expansion. All clients — the CLI/TUI, CastCodes, comux, or your own integration — access the same session state through the same-user local IPC API (coven.daemon.v1). An optional memory dashboard installs separately as @opencoven/coven-memory-dashboard. Running bare coven opens the interactive UI.
- A developer switching between Codex, Claude Code, and GitHub Copilot CLI in one repository wants session history, event logs, and state managed locally by one daemon.
- A team that needs to audit what agents did in a project: Coven records PTY execution and events, browsable via coven sessions.
- A tooling author building their own interface can integrate over the same-user local IPC API (coven.daemon.v1 contract) instead of reimplementing the execution layer.
- Security-conscious users want cwd validation, PTY lifecycle, and IPC enforcement decided centrally by a Rust daemon rather than by clients.
- An adapter author can implement and plug in a new coding-agent CLI following the harness adapter contract in docs/HARNESS-ADAPTERS.md.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Install / run
npm install -g @opencoven/clinpm install -g @opencoven/coven-memory-dashboard
- Config files
.env- Runtime
- Node.js 24+
- Install notes cover
- Windows · macOS · Linux
How do you install or deploy this agent?
Install via npm (the universal wrapper auto-selects your platform package), then run the self-check:
bash
npm install -g @opencoven/cli
coven doctorPlatform packages: @opencoven/cli-macos (Apple Silicon), @opencoven/cli-macos-x64 (Intel), @opencoven/cli-linux-x64 (glibc x64, Alpine unsupported), @opencoven/cli-windows (Windows x64). The optional memory dashboard requires Node.js 24+ and installs separately:
bash
npm install -g @opencoven/coven-memory-dashboardnpm, cargo, and source install routes are documented at https://docs.opencoven.ai/docs/guide/install. Harness logins are provider-owned (e.g. coven setup codex for Codex).
How do you use this agent?
Complete one full flow inside your target project directory:
bash
cd /path/to/your/project
coven setup codex
coven doctor
coven daemon start
coven run codex "fix the failing tests"
coven sessions
coven daemon stopRunning bare coven opens the interactive UI. The CLI command reference is at https://docs.opencoven.ai/docs/cli. For contributors: run python scripts/check-secrets.py before every PR and never commit runtime state (.coven/, *.sqlite*, *.sock, .env*, *.key).
What are this agent's strengths and limitations?
- Multi-harness neutrality: Codex, Claude Code, and GitHub Copilot CLI all run inside one project boundary, avoiding lock-in to a single vendor's agent.
- The Rust daemon is the sole authority boundary — cwd validation, PTY, and IPC decisions are architecturally separated from clients.
- Local-first: session state persists to on-machine SQLite with auditable event logs and a documented IPC contract (coven.daemon.v1) for third-party integrations.
- MIT licensed, external PRs open, distributed across macOS/Linux/Windows x64.
- Early MVP — the README says it is usable for adventurous developers but expects rough edges, so it is not a conservative production choice yet.
- Session logs capture harness output; if a harness dumps secrets, Coven logs them — the project advises against untrusted prompts in sensitive repositories.
- Linux distribution is glibc x64 only (no Alpine), and the memory dashboard additionally requires Node.js 24+ and a separate install.
- Until adapter contracts stabilize, harness support is deliberately limited to Codex, Claude Code, and GitHub Copilot CLI.
How does this agent compare with similar options?
Coven positions itself explicitly as a shared runtime substrate beneath coding-agent CLIs like Codex, Claude Code, and GitHub Copilot CLI: those tools each own their session and permission models, while Coven adds a unified session lifecycle, SQLite persistence, and an authoritative daemon so any harness's work is visible and coordinated within the same project.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Coven This agent | 66 · Some gaps | CLIFree | ★ 76 | today | Rust | Codex · Claude Code |
| Yardlet | 80 · Good | Desktop appFree | ★ 46 | today | Swift | Codex · Claude Code |
| OpenAgentd | 53 · Major gaps | Desktop appFree + model costs | ★ 217 | 1d ago | TypeScript | ChatGPT · OpenAI API · Claude API |
| Puppetmaster | 73 · Some gaps | CLIFree + model costs | ★ 479 | today | Python | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
The packet describes a daemon-owned authority boundary, same-user local IPC, constrained harness IDs, path and argv validation, event redaction, and raw sensitive artifact persistence disabled by default. The installation guide says provider credentials remain with harnesses, and the included HTTP skill requires confirmation before mutating requests. Deductions reflect the stated COVEN_HOME hardening gap and file-based artifact key that is not OS-keychain managed; the packet does not establish comprehensive dependency vulnerability management. Rollback and attribution detail is limited, though the security reporting route and maintainer information are explicit.
The README, CLI help, harness guide, and security policy are broadly consistent about local project scope and harness boundaries. The policy names fail-closed checks and verification families. No execution evidence is required for this static review; dependency availability is only partly covered by platform packages and external harness prerequisites. Doctor diagnostics, install hints, and permission troubleshooting provide useful recovery guidance, but the sample does not establish complete failure handling.
The material targets developers and covers multiple harnesses, CLI and daemon usage, IPC clients, and several platforms. It clearly distinguishes supported, experimental, unsupported, and remote-access boundaries. The deduction reflects uneven skill trigger precision: the repository runtime focus is clear, but the sampled cleanup skill has a broad trigger and only a weak connection to the main runtime.
The repository has clear README navigation, source-adjacent contract references, installation and uninstall entry points, detailed harness installation steps, examples, and troubleshooting. The MIT license text is complete. The security policy labels pre-1.0 status, supported and experimental surfaces, and limitations. Deductions reflect the lack of a supplied complete changelog or clear release cadence; maintenance responsibility has a reporting route, contribution guide, and named author, but support is limited to the current minor line with no LTS commitment.
The product brings coding harnesses into project-scoped sessions with daemon authorization and a persistent event ledger, with CLI flows and a machine-readable interface for practical coordination. The packet provides no quantified benefit or full cost accounting; users still install, authenticate, and maintain external harnesses, and the project describes itself as an early MVP.
Important security claims point to named contracts, authority boundaries, and verification families, while CI lists guard scripts and test commands. The policy separates enforced properties, residual risks, and design goals. Cross-source support is strong but not all cited material is included in this sample, and static review cannot establish that listed checks passed.
- This is pre-1.0 software. The security policy says harnesses running as the same user are not sandboxed by Coven; avoid untrusted prompts or harnesses in sensitive repositories.
- Session logs can capture harness output; do not paste secrets into prompts. Enabling raw artifact persistence stores unredacted data, although it is off by default and encrypted.
- The policy identifies COVEN_HOME ownership and permission checks as a hardening gap; do not expose local IPC to a network.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
v0.5.0 Coven v0.5.0
Release notes excerpt
Coven v0.5.0 This release advances Coven's supported release family to 0.5.x, fixes mobile signed-request replay retention, and pins Coven Code 0.9.0. Source manifests continue to use release-time version stamping. Changes since v0.4.10: - Retains mobile signed-request nonces through their complete accepted signature-validity window, including clock skew and the inclusive expiry boundary, and keeps retired requests expired after an in-process clock rollback. …View on GitHub ↗ -
v0.4.10 Coven v0.4.10
Release notes excerpt
Coven v0.4.10 A fresh install can now create its first familiar without Cave, and Copilot replies reach the stream on Windows. ```sh npm install -g @opencoven/[email protected] coven doctor ``` CLI - coven familiar create <display name> (also coven familiars create) adds one familiar to familiars.toml and seeds <COVEN_HOME>/workspaces/familiars/<id>/ with starter SOUL.md and IDENTITY.md. --id, --emoji, --role and --description are optional. - The roster is written under an exclusive lock and staged beside the …View on GitHub ↗ -
v0.4.9 Coven v0.4.9
Release notes excerpt
Coven v0.4.9 Coven implements every Automations v1 command: all 19 in the command matrix, including run-now, cancellation, retry and recovery. The daemon also keeps one long-lived main session per scope, and the CLI gains coven familiar-ledger and coven eval-loop. ```sh npm install -g @opencoven/[email protected] coven doctor ``` Automations - Five commands that v0.4.8 refused, or handled only through a compatibility path, are implemented. All five are owner-only. - occurrence.runNow.v1 starts one occurrence now. Replaying a request …View on GitHub ↗
FAQ
Does it cost anything?
Where do my code and session data live?
Can I swap models or harnesses?
How secure is it? Can I run untrusted prompts?
Which platforms are supported?
Is Coven open source?
Is Coven still maintained?
Who makes Coven?
What is Coven's official website?
Thanks — we use this to improve the page.