Coven
A local runtime for durable, auditable coding-agent work.
1 min read
Canonical Coven runtime manual
From install to evidence.
Start with one recorded coding-agent session, then move outward into the CLI, daemon, harness, memory, and local API contracts that make the work durable.
First-session path
Four moves from readiness to recovery
The primary journey stays narrow. Advanced runtime and integration material only appears after the first useful loop is complete.
Prepare
Install Coven, verify the local boundary, and connect a harness you already trust.
coven doctorOpen guide Run
Launch one project-scoped session without moving provider credentials into Coven.
coven runOpen guide Inspect
Read the session record, event stream, and logs after the harness exits.
coven sessionsOpen guide Recover
Diagnose readiness, daemon, project, and harness failures in one ordered path.
coven doctorOpen guide Contract map
Choose the surface you need
Every section declares its stability and links to the repository that owns the underlying facts.
Guide
Onboarding, installation, concepts, architecture, and ecosystem boundaries
Source · OpenCoven/coven-docsCLI Reference
Commands, options, diagnostics, sessions, and maintenance
Source · OpenCoven/covenHarnesses
Harness installation, authentication, project roots, and adapter behavior
Source · OpenCoven/covenDaemon
Lifecycle, configuration, local IPC, security, observability, and recovery
Source · OpenCoven/covenMemory + Models
Memory layers, search, provider boundaries, and local model behavior
Source · OpenCoven/covenCoven Code
Coven Code installation, providers, commands, configuration, and recovery
Source · OpenCoven/covenAPI Reference
Generated stable daemon API operations, schemas, and local examples
Source · OpenCoven/covenReference
Authentication, safety, API behavior, and operational troubleshooting
Source · OpenCoven/coven-docsExperimental
Shipped foundations that are not supported production workflows
Source · OpenCoven/covenRelease evidence
The public manual ships with the product contract.
Generated API pages, browser routes, machine-readable exports, deployment commit attribution, and upstream source watches are verified independently of the hosting provider.
Last updated on