Install Harness CLIs
How to install Codex and Claude Code for Coven, how detection works, and how to recover from PATH or auth setup problems.
1 min read
Coven does not bundle harness CLIs. Each harness is installed and authenticated through its own provider's tooling, then Coven detects the executable on PATH.
Supported v0 harnesses
| Harness id | Executable | Install command | Provider login |
|---|---|---|---|
codex | codex | npm install -g @openai/codex | codex login |
claude | claude | npm install -g @anthropic-ai/claude-code | claude doctor |
After installing, run:
coven doctorcoven doctor reports whether the executable is available. It does not read provider credentials; the login command remains provider-owned.
Detection flow
Only built-in harness ids are accepted. A client cannot send an arbitrary executable path through the daemon API.
PATH and daemon environment
If you install a harness after the daemon is already running, restart the daemon so the process environment is fresh:
coven daemon restart
coven doctorIf coven doctor still reports a missing harness, check duplicate or unexpected binaries:
which -a codex
which -a claudeFirst launch
coven run codex "describe this project"
coven run claude "review this project for risky defaults"Use Provider auth boundary if a harness launches but exits with a provider login error.
Last updated on