oxi — User Manual¶
Version: 0.1.0a4 · Status: Alpha (first-fork-ready)
oxi is a forkable autonomous coding orchestrator. It reads a markdown roadmap, dispatches parallel Claude Code sessions to implement each item, opens pull requests, runs a critic review, and keeps a daily spend ledger — all in a single headless loop you can install in one command.
What oxi does¶
- Reads your roadmap — a
roadmap.mdwith tiered items (T0,T1, …). - Picks the next item — Tier 0 before Tier 1, highest-priority first.
- Provisions a worktree — isolated git workspace under
.oxi/worktrees/. - Spawns a Claude Code session (
claude -p) in that worktree with a focused brief. - Waits for a PR — the session commits, pushes, and opens a GitHub PR.
- Runs a critic pass — a second model invocation reviews the diff.
- Optionally merges — if
auto_merge=Trueand critic approves, the PR merges. - Records cost — every session's spend is tracked against your budget caps.
You review PRs at step 6. The engine never touches main without your sign-off, or without an explicit auto_merge=True policy you configured.
Who this is for¶
Solo engineers and small teams who want to ship roadmap items faster by having Claude implement them, with human review at PR time. oxi is not a chat assistant, a CI/CD system, or a multi-tenant SaaS — it is a local daemon you run against your own repo.
Sections¶
- Install — from
pip installto first PR in under ten minutes - Roadmap format — how to write items oxi can parse
- Adapter — configuring oxi for your project
- Running dispatch — tick, kill, unkill, status
- Dashboard — the localhost HTML dashboard
- Budget caps — daily limits and per-task ceilings
- Safety rails — auto_merge discipline, path isolation, env whitelist, SQL safety
- Dogfood loop — using oxi to ship oxi
- Doc lint — lychee + markdownlint: broken-link detection and style enforcement
- Rollback — stopping and reverting
- Troubleshooting — common failure modes