Skip to content

Ultimate Harness Documentation

Ultimate Harness is a runtime-agnostic development harness for planning, launching, observing, verifying, and promoting agentic software-development work across multiple coding agents.

The core design goal is portable discipline: a project should be able to use multiple coding-agent runtimes without losing its specifications, skills, workflow state, audit trail, sandbox boundaries, or human approval checkpoints.

For the active roadmap (epics, in-flight slices, recently shipped), see ROADMAP.md.

  1. Quickstart — install, initialize, run, verify, and inspect a mission.
  • Operator handbook — the operating loop: dispatch, guard, supervise, watch and stop, settle, verify, review, integrate, prove.
  • Known issues — open defects, gaps and unproven claims.
  • Orchestrator guide — mission lifecycle, team execution, observability, human decisions and CLI reference.
  1. Configuration — project state, env vars, and runtime overrides.
  2. Runtime targets — supported runtimes and adapter boundaries.
  3. Vision — what UH is, who it’s for, and what we won’t accept.
  4. Glossary — shared terms used across the project.
  5. Product requirements — what the harness is for and who it serves.
  6. Architecture overview — major components and boundaries.
  7. Runtime adapter contract — what every adapter implements.
  8. Mission packet schema — the portable work-request format.
  • Native runtime events — adapter event contracts, supervision and accounting boundaries.
  • Tool guard — path-only policy, enforcement seams, denial reasons, and artifacts.
  1. Verification and promotion — how sandbox work becomes canonical work.
  2. BMAD agent map — how BMAD-style roles map into Ultimate Harness.
Adapter Status Doc / Runbook
hermes active Runtime adapter contract defines the shape; src/adapters/hermes.ts is the reference implementation.
codex active Codex adapter design, Codex E2E smoke
hermes-proxy active Hermes proxy adapter, setup, E2E smoke
openrouter active OpenRouter setup
anthropic experimental Anthropic setup — native pay-per-token Messages API (UH-136).
pi active Pi setup
oh-my-pi active Anthropic via oh-my-pi — covers the OMP routing path and its ToS posture.
command-code active Tool guard, Acceptance runbook
claude-code integration incomplete Runtime targets — native CLI execution and current limitations.
  • Acceptance status — generated view of the registry and locally available evidence; a clean checkout contains no execution history.
  • Acceptance runbook — register, run, inspect, and regenerate acceptance evidence. For issue-level state and upcoming epics, see ROADMAP.md.