If you run an AI coding agent — Claude Code, Codex, Gemini, Aider, and more — the ox CLI gives it your team's full context at startup and captures what it does back to your Ledger.
Your agent stops starting from zero. It starts from where your team left off, then leaves a record the next session can build on.
The CLI plus adapter model
ox is a single CLI that connects your repo to SageOx. Each supported agent gets a thin adapter that knows how to inject context into that agent and capture its sessions — so the same workflow works whether you drive Claude Code, Codex, or anything else.
The loop is the same across every agent:
- The agent runs
ox agent primeat session start. - Team Context flows in — conventions, decisions, domain terms, prior work.
- The agent works.
- The session is captured to the per-repo Ledger and summarized.
Depth varies by agent. Claude Code is the deepest integration; others get the same priming and capture with fewer real-time touchpoints. See coding agents for the support matrix.
Start here
| Page | What it covers |
|---|---|
| How it works | The prime-work-capture loop, and what any agent receives |
| Supported coding agents | Supported agents and per-agent depth |
| SageOx + Claude Code | The deepest, Gold-tier integration |
| Session recording | Why and how coding sessions become team memory |
| CodeDB | Semantic code navigation your agent can query |
| Build a custom adapter | Wire up an agent ox doesn't support yet |
| Agent factories | Orchestrators and parallel agents |
What's next
- How it works — start with the general model
- ox CLI reference — every command and flag