Documentation

Run the room, by the book.

Everything o8 does, surface by surface — written to be clear for you and queryable by your agents. Each page is stamped against the build it describes, so you can tell when one has gone stale.

Building with an agent? Point it at /llms.txt for the map, or /llms-full.txt for the whole corpus. Every page has a raw .md twin (append .md to any doc URL).

Start here

What is o8?

o8 is a control room for autonomous engineering — one orchestrator dispatches a fleet of coding agents, a governance layer reviews every diff, and nothing risky merges without your sign-off.

Getting started

Install o8, sign in, bring your keys, and run your first dispatch.

Concepts

The eight primitives o8 is built on — runtime, agent, session, packet, lane, mission, review, approval — and how they fit together.

Control Room

The IDE-shaped pane you run the fleet from — the orchestrator chat, the panels, sessions, and the o8.md workspace spec.

Agents & Dispatch

Dispatching work

How a task becomes a merged change — missions, isolated worktrees, the runtimes, and where you sign off.