A session enters a project.
Coven binds work to the current local project and restores durable session context rather than treating every terminal process as the whole system.
Current runtime behavior
The local layer your agent sessions share.
Coven sits at the local project boundary. Your coding harness still reasons and edits; Coven owns the durable session state, claims, execution records, and guard decisions those sessions need to coordinate safely.
One project, shared local evidence.
The runtime does not make every session one agent. It gives independent sessions a common place to state intent, preserve records, and encounter explicit authority boundaries.
Intent becomes inspectable.
Claims and records make overlapping work visible, so sessions do not need to coordinate through prompt folklore or silent last-writer-wins behavior.
Protected work can wait.
Guarded local operations can pause for human approval instead of inferring authority merely because an agent has context or filesystem access.
The record survives the terminal.
Durable runtime state makes claims, sessions, and evidence inspectable after an individual shell or harness process exits.
What Coven owns—and what it does not.
Keeping these boundaries explicit prevents the runtime from quietly becoming a second identity protocol, orchestration plane, or product UI authority.
Runtime authority
Durable session state, claims, local execution, persistence, and enforcement at the project boundary.
Not identity definition
The Familiar Contract defines the governed familiar self; Coven consumes authorized identity rather than redefining it.
Not orchestration policy
Psyche owns task, lane, lease, approval, receipt, and recovery protocol semantics across orchestrated work.
Verify it from one project.
The canonical foundation remains deliberately small.
npm install -g @opencoven/clicoven doctorcoven