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.
WebUI, TUI, and Desktop stay thin and consume one OAH-compatible contract.
02 Control PlaneAPI, controller, placement, queues, and rebalance coordinate concurrent workspaces.
03 Execution PlaneEmbedded and sandbox workers execute runs while preserving workspace state boundaries.
04 Storage PlanePostgreSQL, 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.
Related paths
Turn architecture into the next maintenance move.
Architecture is most useful when it points to the exact layer you need to modify, operate, or expose.
Configuration files explain which agents, models, skills, hooks, and MCP servers the engine can see.
API Map boundaries to endpointsTranslate architecture ownership into resources, streaming events, schemas, and client expectations.
Operations Deploy the planes separatelyMove from architecture diagrams into split deployment, queue reliability, storage, and runbook decisions.