OpenCoven
Join the Coven ✦

public beta free & open source · runs locally

Summon agents
that remember.

Coven gives each AI agent a name, a memory, and a place in your work. Close the terminal tonight — tomorrow Hexi still knows your branch, your conventions, and where you left off.

Download for macOS CovenCave · .dmg · signed · free Download for iOS CovenCave · TestFlight · iPhone & iPad
Join Discord Read the docs ↗
coven · session local
coven attach hexi --project ./opencoven
H
Hexi code steward · tools · git
awake
memory restored 128 notes · 47 days
resumed feat/runtime-attach · 4 files staged 2h ago
prefers terse PR summaries, no trailing recap persisted
  1. day 1 summoned Hexi, learned the repo
  2. day 9 picked up your review style
  3. day 23 shipped feat/runtime-attach
  4. day 47 · today still remembers all of it
Drives the agent CLIs you already use
Claude Code · Anthropic Codex · OpenAI + more adapter-ready

Why Coven

01

AI that can stay

Familiars keep a name, role, memory, and place in the work across every session.

02

Local runtime substrate

Coven keeps execution bounded to explicit projects and tools. Not a harness — the layer beneath.

03

Shared ecosystem

Codex, Claude Code, CastCodes, dashboards, and docs built to fit together.

04

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.

Coven architecture: harness, runtime, and project layers harness layer coven runtime your project project-scoped boundary output · memory Codex Claude Code + Future Sessions Memory Adapter Tool gateway Filesystem Git Terminals Docs

coven

Harness adapter

Translates each harness's native protocol into one neutral runtime interface.

  • Codex streams, Claude Code tool calls, whatever comes next
  • Sessions, memory, and tools stay harness-agnostic
  • New harnesses slot in without ripple effects elsewhere

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.

context project: opencoven · stack: astro + vanilla
preference prefers terse PR summaries · no trailing recap
state resumed feat/interactive-deep-dive · 4 files staged

Compare

Why Coven, not just a harness?

Same agent CLIs, different runtime around them. Open a capability 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
Raw harness No
Other tools Limited
Coven Yes

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.

Raw harness Limited
Other tools Limited
Coven Yes

Most tools assume the current directory and trust you to remember. Coven binds every session to a project record — filesystem, git, terminals, and docs all scoped to that root.

Raw harness No
Other tools Limited
Coven Yes

A raw harness only knows itself; suites bundle one or two. Coven exposes a neutral adapter contract so Codex, Claude Code, and future CLIs all run the same way.

Raw harness Limited
Other tools Limited
Coven Yes

Each harness has its own permission model and prompt style. Coven funnels every tool call through one auditable gateway: fs, git, exec, web — same contract, visible logs.

Raw harness No
Other tools Limited
Coven Yes

Raw harness sessions die with their terminal. Coven keeps the PTY alive in the runtime, so you can detach, reboot, and pick up exactly where the agent left off.

Raw harness Yes
Other tools No
Coven Yes

Raw harnesses already run locally; SaaS suites don't. Coven is open and inspectable end-to-end — you can read what it runs, swap the adapter, or replace the gateway.

Quick Start

Run your first familiar in three commands.

Coven runs locally inside the projects you already have. Install, verify, and summon — memory persists across every session.

  1. Step 1 · Install

    Add the Coven CLI

    npm install -g @opencoven/cli

    expect ✓ coven ready on PATH

    Installs the coven command globally through npm.

  2. Step 2 · Verify

    Check your environment

    coven doctor

    expect ✓ Claude Code · Codex detected

    Detects the supported harnesses on your machine and confirms the runtime is healthy.

  3. Step 3 · Summon

    Wake your first familiar

    coven run "hai world"

    expect ✦ Hexi awake · 128 notes · 47 days restored

    Launches a project-scoped session through Coven's managed PTY, bound to the current directory — with Hexi's memory already loaded.

Read the full docs View on GitHub ↗

Ecosystem

The Circle is Open.
Step Inside.

Workspace for familiar agents — the open runtime, the companion terminal, and the builders shaping it. Pick a way in.