OpenCoven

public beta free · open source · local-first

Summon once.
Remember forever.

A familiar is an AI agent with a memory, bound to your project. Close the terminal and the context, conventions, and unfinished work stay.

the runtimes it speaks

bound to the tools you already own

OpenAI Codex coven run codex "explain this repo"
  • OpenAI Codex coven run codex "explain this repo"
  • Claude Code coven run claude "explain this repo"
  • GitHub Copilot coven run copilot "explain this repo"
  • OpenCode coven run opencode "explain this repo"
  • Grok Build coven run grok "explain this repo"
  • Hermes Agent coven run hermes "explain this repo"
  • OpenClaw coven run openclaw "explain this repo"

I the boundary surface · runtime · project

Three layers. Only one is yours to defend.

OpenCoven is the substrate under your AI tools — an agent’s memory lives inside your project, not in the tool. Change the surface as often as the work calls for it. Continuity lives in the substrate, and the project boundary never leaves your machine.

Surface

Desktop and Mobile Applications

Swappable by design.

Codex, Claude Code, Coven Code or Cave — pick the interface that fits the task and change it whenever you like.

cave desktop · cave ios
familiar.ledgerlocal

HHexi · code steward● ready

SESSIONfeat/runtime-attach

MEMORYproject memory restored

4 files staged · tests pending

Hexi● syncedmemory ✓
what stays here

chosen interfaceswappable

keyboard, panes, promptper surface

nothing durableby design

Read the architecture docs ↗

Runtime

Portable Memory for Agents

Continuity lives here.

Sessions, familiar memory, adapters and tool permissions live here — between the surface you use and the project you own.

coven-memory · the project record
coven-memorylocal

prefers terse PR summaries remembered

smallest correct patch remembered

verify before commit remembered

— portable · travels with the project
what stays here

sessions + historylocal

familiar memorylocal

tool permissionsexplicit

Read the architecture docs ↗

Boundary

Isolated Working Directories

Authority stops here.

Filesystem, Git, terminals and docs stay inside the project you named. Provider keys stay with the provider.

inside the boundary you named
inside · ./opencoven

filesystem.gitterminalsdocs

sessions read and write here — nowhere else
outside the wall

provider keysother projects

no session crosses in
what stays here

filesystem + Gityours

terminalsyours

provider keysprovider

Read the architecture docs ↗

II the surfaces start where the work is

One substrate. Three ways in.

Every surface writes to the same local record. Start wherever the work is — each path leads to its own verifiable Quick Start.

Connect the desktop app to its local Coven runtime, with an optional iOS companion handoff.

A visual home for familiars, projects, and sessions, with an optional iOS companion.

Native app macOS · Windows · Linux · iOS
3 familiars · locallive

HHexifeat/runtime-attach● working

SSageruntime-notesidle

iOS companion paired
Open guide

Install the shared OpenCoven runtime, check your project, and start a provider-backed session.

Terminal-first control, scripts, and a shared runtime for the OpenCoven ecosystem.

Recommended foundation macOS · Linux x64 · Windows x64

❯ coven doctor

✔ project   ./opencoven ✔ harness   codex ✔ daemon    running

❯ coven run codex "explain this repo"

session   01JC7F · feat/runtime-attach
Open guide

Use the unified Coven CLI to enter an interactive, provider-backed coding workspace.

An interactive coding-agent TUI inside an existing project.

Beta macOS · Linux · Windows
src/
tests/
README

+ adapter boundary- legacy shim▍ awaiting review

Open guide

still decidingLet the runtime pick the surface.Run one command in your project. Coven reads what is already there and names the next verified step.

coven doctor

III the invocation ~2 minutes · no account

Three commands to first summon.

Nothing to sign up for. Install the runtime, let it read your project, then bind a familiar to it — each step runs as you scroll.

  1. + @opencoven/cli@1.4.2

    coven — the local-first familiar runtime

    Expect: the help screen lists every top-level command.

  2. ✔ project detected ./opencoven

    ✔ harness codex (ready)

    ✔ daemon running

    Expect: actionable guidance for any missing setup.

  3. session 01JC7F · feat/runtime-attach

    harness codex status complete

    memory project record updated

    Expect: the history row shows id, harness, title, status.

coven — zsh 01 · Install

npm install -g @opencoven/cli

+ @opencoven/cli@1.4.2

coven — the local-first familiar runtime

Expect: the help screen lists every top-level command.

After the third command the familiar is yours — pick a surface and its guide carries you the rest of the way.

IVthe summoningbelong on your terms

Your familiar. Your tools. Your machine.

Start with one product, keep the runtime inspectable, and add community only when it helps.

❯ copy · paste · summon

npm install -g @opencoven/cli

3surfaces, one record

0accounts required

100%local by default