The broader project family and organization around Coven, CastCodes, Cast Agent, Cast Codes, and integrations.

Use this when talking about the ecosystem, not one runtime process.

The local runtime substrate and command-line product for launching and supervising agent work.

This owns local sessions, harness runs, logs, and the daemon API.

The user-facing command surface for the coven binary.

Package names live under OpenCoven, product docs say CovenCLI, and shell examples still run coven.

The first-party OpenCoven workspace for panes, files, diagnostics, agent lanes, sessions, review, and merge flow.

It is the visible cockpit for agent work, while Coven remains the local runtime boundary.

The Coven-native substrate manager and AI agent backend inside CastCodes.

It can collect workspace context and surface Coven sessions, but it does not replace daemon validation.

The portable intent grammar for switching, delegation, broadcast, status, resume, and handoff requests.

Cast Codes make intent portable across clients without becoming permission or policy.

Any process or UI that talks to the Coven daemon instead of launching harnesses directly.

Clients are convenience layers, not trust roots.

A supported coding-agent CLI that Coven can launch and supervise.

Harnesses do the agent work; Coven wraps them with project scope, PTY handling, and session records.

The external model or agent service used by a harness.

Coven does not store provider credentials; each harness keeps its own auth flow.

The external package @opencoven/coven, which lets OpenClaw use Coven through the socket API.

It bridges ecosystems without making Coven part of OpenClaw core.

A named agent persona with identity, memory, tools, and policy in the broader Coven and OpenCoven language.

Familiars explain the human-facing layer above raw harness processes.

The local Rust process that owns live session state and exposes the socket API.

The daemon is the authority boundary for launches, input, kill requests, and session state.

A Coven-owned record of one harness run.

Sessions give clients a stable object to list, inspect, replay, archive, summon, or sacrifice.

An append-only record for session output, exit, or metadata.

Events make work replayable after a process exits or the daemon restarts.

Coven local SQLite database for session metadata and append-only event history.

It preserves runtime records without putting sockets, logs, or databases in source control.

A pseudoterminal used to run terminal-native harnesses.

PTYs let Codex and Claude Code behave like normal CLIs while Coven records their output.

The default CovenCLI interface for free-form task text, slash commands, and menu navigation.

It keeps the terminal interface centered on sending work, not configuring machinery first.

The local HTTP-over-Unix-socket API exposed by the daemon.

It is the compatibility boundary for local clients and integrations.

The named compatibility contract exposed by the daemon socket API. Current stable value: coven.daemon.v1.

Versioning lets clients detect which response shapes and behaviors they can rely on.

A discoverable daemon or adapter feature returned by GET /api/v1/capabilities.

Capabilities let clients show what is available without guessing.

The daemon layer that exposes capabilities and routes known action ids to owned adapters.

It gives clients a safe discovery and action path while unknown action ids fail closed.

Agent Client Protocol, used here as an integration surface for external agent runtimes and OpenClaw compatibility.

Coven is not an ACP implementation; the bridge maps external runtime events into Coven sessions.

The explicit repository or project boundary for a session.

The daemon validates this boundary before launch so a client cannot silently widen scope.

The launch directory for a harness session, after canonicalization inside the project root.

It lets work start in a subdirectory without escaping the project boundary.

Coven human-friendly session-management verbs.

They keep product language memorable while the safety behavior stays precise underneath.

Hide a non-running session from the active list while preserving its record and events.

Archive is the reversible way to clean up active views.

Restore an archived session to the active list and then replay or follow it.

Summon brings history back into view without rerunning the harness.

Permanently delete a non-running session and its events.

Sacrifice is intentionally irreversible and should stay gated in clients.

The layer allowed to validate and enforce sensitive runtime behavior.

In Coven, that layer is the daemon, not a client, Cast Code, or UI label.

A component trusted to make security-relevant decisions.

Clients are not trust roots; they request, display, and guide.

Write-side operations in coven pc that mutate system state, such as process termination or cache deletion.

Relief operations are useful but sharp, so they require an explicit --confirm flag.

A macOS-first system diagnostics and relief subcommand.

It reports CPU, memory, disk, and top processes, with write operations gated behind confirmation.

The local directory where Coven stores daemon, socket, database, and runtime state when configured.

Runtime state belongs outside source control and should not be committed.

A visible workspace for steering and reviewing agent work.

Use it for CastCodes-style experience, not for daemon internals.

The local foundation that lets agent tools run, persist, and reconnect.

It names the layer beneath familiar personality and client UI.

A compact syntax for expressing what a human or agent wants to happen.

This keeps Cast Codes framed as routing intent, not authorization.

Multi-harness handoff and task routing that are roadmap work, not current public CLI/API behavior.

It prevents docs from promising features before the runtime contract exists.