Hermes Conductor

What Hermes Conductor does

The conductor is a route-only Hermes profile that decomposes work, fans it out to isolated git worktree lanes, verifies the results and integrates them into a canonical branch. Each lane can run a different coding CLI, such as Claude Code, OpenCode, Codex CLI or MiMo. The controller never trusts a worker's own report: it re-runs the tests itself and closes a card only with evidence such as commit IDs and command output.

The patterns come from 18 production boards, 367 cards and 566 agent dispatches. The README catalogs the failures behind them: self-report trust, two worker cards landing in one checkout, stale-base auto-promotion, approval deadlock loops that burn tokens overnight, and evidence-free done states. It includes two recorded demos, a native dispatch cycle and Claude Code as a headless lane executor through claude -p. It also describes an SDK-based lane runner with per-lane budget caps, max_turns, hard timeouts, explicit tool grants, provenance checks and JSON receipts.

Key features

• Route-only Hermes controller profile that decomposes, fans out, verifies and integrates
• Isolated git worktree lanes, one per coding CLI
• Controller re-runs tests instead of trusting agent self-reports
• Lane runner with budget caps, max_turns and fail-closed provenance checks
• JSON receipts attached to cards as machine-checkable evidence
• Recovery playbooks for failures such as approval deadlock loops

When to use it

• Running Claude Code, OpenCode and Codex CLI side by side on separate cards of one Hermes board
• Preventing two worker cards from mutating the same checkout
• Requiring commit IDs and command output before a card can close

Who it is for: Developers who use Hermes Agent as a controller and dispatch work to external coding CLIs.

How it fits with Hermes Agent

Built around Hermes Agent: the controller is a Hermes profile working through the Hermes kanban board and gateway dispatcher.

Note: The structured SDK lane runner described in the README is still being packaged for separate publication.

FAQ