Identity
A familiar is intended to have a stable governed root, declared scope and memory boundary, attributable revisions, and explicit principal binding.
Identity-preserving familiar infrastructure
Give your agents continuity. Keep authority local.
OpenCoven is building governed familiar identities that can carry memory, provenance, and permissions across the surfaces where they work. Today, Coven proves the local foundation through shared claims, durable records, and human-approved guards.
Trust starts with boundaries.
The landing page is not a protocol authority. It presents only evidence-backed product state and clearly marks category direction that is not yet complete.
Local-first Current Coven proof runs at the local project boundary.
Open source Public repositories, schemas, releases, and implementation evidence.
Provider-backed Supported harness sessions sit behind the shared runtime boundary.
Human-approved guards Protected local actions can wait for explicit principal approval.
Verifiable artifacts Cave release evidence links to GitHub attestations.
Identity → authority → continuity.
These are separate concerns. Identity describes which familiar is being embodied. Authority governs protected change. Continuity records why a later embodiment should or should not be considered the same familiar.
Authority
Today, Coven can hold protected local actions for human approval. The broader principal-authentication and cross-surface authority profile remains ongoing protocol work.
Continuity
Continuity is evidence that a later embodiment or revision is the same familiar, a successor, a fork, a restored state, or a different root—not merely the same prompt or display name.
- Familiar Contract defines the governed familiar self.
- Threads / Coven enforce protected mutation and runtime authority.
- Psyche snapshots authorized identity into orchestration.
- Coven runtime owns local session persistence and execution.
- Cave · Code · GitHub · SDK are product and client surfaces.
A concrete local proof.
The strongest current story is deliberately smaller than a simulated operating system: two sessions want the same protected surface, Coven holds the conflict, and the principal decides what happens next.
Available today
Two sessions claim the same surface.
The shared local record makes competing intent visible instead of letting one session silently overwrite another.
session-a → claim src/auth.ts · session-b → competing claim Available today
Coven holds the second protected write.
The runtime records why the operation is waiting, preserving an inspectable boundary instead of guessing on behalf of the principal.
guard → held · reason: overlapping protected surface Available today
The principal decides.
Approval, redirection, or rejection remains a human decision; the evidence stays attached to the local workflow for inspection in Cave.
principal decision → approve | redirect | reject Choose the surface that matches the job.
Product status and destinations come from the checked-in public registry rather than duplicated homepage strings. Archived predecessors are intentionally omitted from the recommended start path.
Terminal runtime
Coven CLI
Install the shared OpenCoven runtime, check your project, and start a provider-backed session.
Best for: Terminal-first control, diagnostics, scripts, and the shared foundation for current OpenCoven surfaces.
macOS Apple Silicon · glibc Linux x64 · Windows x64 · also available for macOS Intel x64
Install the CLIInteractive agent TUI
Coven Code
Use the unified Coven CLI to enter an interactive, provider-backed coding workspace.
Best for: An interactive coding-agent cockpit inside an existing project.
macOS Apple Silicon and Intel x64 · Linux x64 and ARM64 · Windows x64
Open Coven CodeVisual desktop home
Coven Cave
Connect the desktop app to its local Coven runtime, with an optional iOS companion handoff.
Best for: Visual oversight for projects, familiars, sessions, evidence, approvals, and recovery.
macOS Apple Silicon and Intel x64 · Windows x64 · Linux x64 · optional iOS companion
Download CaveGitHub delivery
OpenCoven for GitHub
Assign bounded GitHub work to a familiar and receive inspectable status, Check Runs, and a draft pull request when commits exist.
Best for: Issue-to-delivery workflows with hosted-gated or self-hosted setup and Cave oversight.
GitHub · hosted beta or self-hosted worker
Choose hosted or self-hostedOne canonical local start.
Install the shared runtime, verify the project, then open Coven. Product-specific branches come after this common foundation.
1
npm install -g @opencoven/cli 2
coven doctor 3
coven