Skip to content

Open Agent Harness Docs

Long-lived agent engine documentation

Organize runtimes with Markdown and run many workspaces in parallel. OAH owns workspace lifecycle, agent execution loops, tool calls, queue coordination, and durable state; WebUI, TUI, and Desktop all connect through the same REST + SSE API.

TypeScript Engine PostgreSQL + Redis REST + SSE Runtime Spec
oah local stack
pnpm install
export OPENAI_API_KEY=sk-...
pnpm dev:cli -- daemon start
pnpm dev:web
pnpm dev:cli -- tui
WebUI TUI Desktop OAH API Controller Workers Storage

Start with runtime confidence, then move through configuration, architecture, and API integration.

Organized around long-term maintenance tasks, not just a list of files.

The docs should help maintainers answer: where should I change this, who does it affect, and how do I verify it?

Client SurfacesWebUI, TUI, and Desktop consume OAH-compatible APIs without owning engine state.
Control PlaneAPI, controller, queues, placement, and rebalance coordinate concurrent workspaces.
Execution PlaneEmbedded or sandbox workers execute runs and synchronize workspace state.
Storage PlanePostgreSQL is the source of truth, Redis coordinates queues, and object storage backs workspace state.