The dock registry
11 runtimes. Chat runs the one you choose in one setting; the harness router can send a spawned subagent to another installed one. A check appears only where a dated row exists on the verification log; today that is 1 cell.
Compatibility, as verified
No Gemini CLI yet.
The harness router (warding route) sends a spawned subagent to another installed harness: flat-rate plan quota before metered spend, the kind of task, and a cooldown after a usage limit or a failed login. It picks a harness and never forwards provider traffic. Registered · unverified.
The order warding planes uses
With the harness set to auto, the first installed runtime in this order is docked. kiro-cli is optional and last: it is used only when nothing else is installed. Set agent.acp_backend to pick one explicitly.
- cursor cursor agent (ACP)
- claude the ACP project's claude-agent-acp adapter, fetched with npx on first run
- codex codex (ACP)
- kimi kimi (ACP)
- dsh dsh launcher (ACP)
- goose goose (ACP)
- grok grok (ACP)
- opencode opencode acp (ACP)
- pi pi (ACP)
- droid droid (ACP)
- kiro-cli kiro-cli (ACP), optional
$ warding planes
Warding planes
harness: auto (selected=claude; vendor CLI optional)
model: built-in catalog (provider translation is not bundled)
docked: claude
never paste provider keys into chat.
warding planes — CLI · 2026-09-26 · claude docked · one harness selected · the role line is omittedHow a harness gets added
One adapter in the runtime registry: the command line that starts the agent over stdio, which protocol family it speaks, a one-line login hint, and the binaries it needs on the path. That is the whole entry. The gateway, the channels and the schedules are shared code. What differs per harness is a short list of capability flags: whether it can share or steer a session, and whether it brings its own sandbox (kiro-cli does, so Warding's own is not layered on top of it).
A harness adapts to the seams the first-class path already runs through. It cannot add a step, a flag or a failure mode to that path, and a harness that cannot fit does not land. What each one can do is then a matter of record, not of the registry: a cell above turns into a check only when a dated row exists on the verification log.
No Gemini CLI yet. If you run one of those, public issue reporting is pending; check source status. Adding one is a small change, not a promise
Review the local beta.
Apache-2.0 source publication is pending. Read the setup notes and verification limits.
Source publication pending
Public source, install commands and downloads are not available yet. A clean install and live workflow are not yet verified.