HarnessesHarnesses
Harnesses
Overview of Coven harnesses, supported v0 adapters, provider-auth boundaries, project-root rules, and adapter direction.
1 min read
A harness is an external coding-agent CLI that Coven can launch inside a project root. Coven owns the PTY, session record, event log, attach/replay flow, and local API boundary. The harness owns the conversation, provider authentication, and tool execution inside its own process.
The current v0 harness ids are codex and claude.
Supported v0 harnesses
| Harness | Harness id | Executable | First command |
|---|---|---|---|
| Codex | codex | codex | coven run codex "fix the failing tests" |
| Claude Code | claude | claude | coven run claude "polish this UI" |
Runtime boundary
Rendering diagram…
The daemon validates the harness id, project root, working directory, session id, live-session state, and control actions. It does not read provider credentials and does not become the provider client.
Read next
- What is a harness? for the concept boundary.
- Install harness CLIs for Codex and Claude Code setup.
- Provider auth boundary before auditing credentials.
- Project roots and working directories before debugging launch rejects.
- Codex and Claude Code for adapter-specific behavior.
- Custom adapters for the future adapter bar.
- Troubleshooting when
coven doctororcoven runfails.
Related
Was this page helpful?No
Last updated on