Open Agent Harness Start

Architecture

One runtime boundary, many product surfaces.

OAH is organized around explicit ownership: clients render and request, the control plane decides, workers execute, and storage keeps durable truth. This page is the fast map before the full design docs.

ClientAPIControllerQueueWorkerStorageEvent stream
01 Client Surfaces

WebUI, TUI, and Desktop stay thin and consume one OAH-compatible contract.

02 Control Plane

API, controller, placement, queues, and rebalance coordinate concurrent workspaces.

03 Execution Plane

Embedded and sandbox workers execute runs while preserving workspace state boundaries.

04 Storage Plane

PostgreSQL, Redis, and object storage split durable state, coordination, and backing store.

Deep dives

Follow the runtime from request to durable event.

These pages explain how an incoming run becomes model input, tool execution, queue state, projection updates, and observable stream events.