Getting started

Five minutes from download to your first reviewed change. The signed, notarized release is for macOS 14+; the current build is Intel and runs on Apple Silicon via Rosetta. Windows 11 has public MSI and EXE previews with checksums and GitHub build attestations; publisher signing remains open. Linux has public AppImage, deb, and rpm previews; the AppImage is GPG-signed, while Linux desktop verification and update delivery remain open.

1. Download

Grab o8 from o8.run/download and choose your platform. No account is required.

2. Install

Open the .dmg, drag o8 to Applications, then right-click → Open the first time so macOS lets it run. After that it auto-updates.

3. Open a local repository

Launch o8 and choose a folder. Local repositories, installed or bring-your-own model tools, and the install-scoped hosted allowance work without an o8 account. The allowance is provisioned on demand when you first invoke an o8-hosted model. Sign in only for portable, account-backed services such as sync, the web console, mobile relay, or Pro.

4. Connect your model access

o8 runs on your model access. Connect a supported CLI subscription or add a provider key in Settings, and the orchestrator and its fleet run on it. A limited install-scoped hosted allowance is also available without sign-in, while portable account services and Pro are optional.

5. Run your first dispatch

Point o8 at a repository, describe a task to the orchestrator, and let it work:

1. The orchestrator plans the task and dispatches it to a coding agent in an isolated worktree.
2. When the agent finishes, the governance layer reviews the diff — and routes risky changes to a second, blind reviewer.
3. The change surfaces for your approval. Nothing merges until you say so.

That loop — dispatch → review → approve — is the whole rhythm of o8. Everything else is a richer way to run it.

Next

• What is o8? — the one-page picture.
• Agents & Dispatch — the worktree model, the escalation ladder, and how review actually decides.