One repo memory, many agents
The ai/ directory carries project rules, decisions, specs, and handoff notes so each terminal CLI starts with the same context.
for senior developers
Stop teaching every agent the same repo.
0dai gives experienced developers one repo-owned context layer for the agent CLIs they already use. Keep the architecture notes, handoffs, and review proof in ai/, then let each tool read the same map.
what changes
The next agent starts where the last one stopped.
Route work without rewriting setup
Claude Code, Codex, Gemini, Aider, OpenCode, and Qoder can read the generated config set; Cursor connects through the MCP/editor bridge.
Receipts before confidence
Every serious change can leave a review receipt, test proof, and issue link instead of a chat-only promise.
proof boundaries
Built for people who review the diff.
This page does not sell a magic editor. It explains the layer around the editors and CLIs: shared files, explicit receipts, and a clear support boundary.
Project memoryRules, decisions, specs, sessions, and experience stay in git-readable files.
Supported surface6 terminal CLIs + Cursor MCP bridge
MCP tools49 free tools; 113 total by plan.
Cursor boundaryEditor bridge support only; no native Cursor adapter is promised here.