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.
Start here
Section titled “Start here”- Quickstart — install, initialize, run, verify, and inspect a mission.
- Configuration — project state, env vars, and runtime overrides.
- Runtime targets — supported runtimes and adapter boundaries.
- Vision — what UH is, who it’s for, and what we won’t accept.
- Glossary — shared terms used across the project.
- Product requirements — what the harness is for and who it serves.
- Architecture overview — major components and boundaries.
- Runtime adapter contract — what every adapter implements.
- Mission packet schema — the portable work-request format.
- Verification and promotion — how sandbox work becomes canonical work.
- BMAD agent map — how BMAD-style roles map into Ultimate Harness.
Adapters
Section titled “Adapters”| 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. |
For issue-level state and upcoming epics, see ROADMAP.md.
Documentation map
Section titled “Documentation map”Research
Section titled “Research”Product
Section titled “Product”- Quickstart
- Configuration
- Runtime targets
- Optional telemetry
- Troubleshooting
- PRD
- MVP scope
- Non-goals
- Personas
Architecture
Section titled “Architecture”- Overview
- Entities
- Runtime adapter contract
- Codex adapter design
- Hermes proxy adapter design
- TUI architecture
- Plugin development
- Mission packet schema
- .harness artifacts
- Skill format
- Sandboxing
- AgentFS sandbox backend (design)
- Verification and promotion
- SDD + TDD + cross-runtime QA
- Telar planning/governance and UH Run Control boundary
Runbooks
Section titled “Runbooks”- Codex E2E smoke
- Anthropic via oh-my-pi
- Hermes proxy setup
- Hermes proxy E2E smoke
- Hermes dashboard plugin
- Using
uh tui - Honcho persistent memory
- Publishing
Workflows
Section titled “Workflows”- Workflow overview
- Research to spec
- Spec to plan
- Plan to mission
- Mission to sandbox
- Verify, review, promote
- BMAD agent map