0dai

One config layer for 7 AI agent CLIs — Claude Code, Codex, OpenCode, Gemini, Aider, Qoder, Cursor.

Install

npm install -g @0dai-dev/cli

Five commands that matter

cd your-project
0dai init      # create ai/ layer, auth, and MCP bootstrap
0dai status    # maturity, swarm tasks, and session state
0dai sync      # refresh ai/ after repo or server changes
0dai run "…"   # split a backlog item into agent tasks
0dai doctor    # health check for credentials, drift, and env

All commands

Start (first 5 minutes):

0dai init                           # create ai/ layer + MCP [--local] [--dry-run] [--minimal]
0dai init --auth-code <code> --code <TEAM-CODE>   # non-interactive auth + activation
0dai doctor                         # check health, credentials, and drift [--drift]
0dai status                         # maturity, swarm, and session state [--json]
0dai quickstart                     # auth, init, doctor, and status in one pass
0dai detect                         # show detected stack
0dai auth login                     # OAuth/device flow [--device] [--no-browser] [--code CODE] [--mcp]
0dai auth mcp                       # store MCP token from current auth or device code
0dai auth status                    # account and usage
0dai activate free                  # claim free activation license

Daily (regular work):

0dai sync                           # update ai/ after repo or server changes [--dry-run] [--yes] [--quiet] [--force]
0dai run <goal>                     # split a backlog item into agent tasks [--dry-run] [--dry-cost] [--agent claude|codex|gemini]
0dai swarm status                   # show queued, active, and done tasks
0dai swarm add                      # queue one task [--task '...' --to agent]
0dai swarm-run                      # add, dispatch, and wait for one swarm task as JSON
0dai harvest                        # convert experience events into candidate lessons
0dai watch                          # live task monitor [--interval N]
0dai reflect                        # session reflection: delivered, delegation, blockers
0dai standup                        # morning voice briefing about overnight agent work
0dai feedback push                  # send feedback to 0dai
0dai feedback retry                 # retry queued feedback after a failed push
0dai persona-simulate "topic"       # focus-group report and optional issue drafts

Pro / advanced:

0dai init-existing                  # existing-repo setup alias for init
0dai project bind                   # bind repository to your 0dai account [--json]
0dai project status                 # local project binding and health [--json]
0dai graph push                     # upload local graph (Pro: edges, Free: nodes)
0dai graph pull                     # download server graph and merge locally
0dai graph status                   # local graph stats and sync state
0dai ci                             # portable CI pipelines and AI-MQ [list|plan|mq-status]
0dai heatmap                        # repo treemap: LOC × agent-edit intensity
0dai session save                   # save session for roaming
0dai provider                       # local provider profiles and direct invoke
0dai models                         # model ratings (--fast/--balanced/--deep/--available)
0dai quota                          # agent subscription usage [--refresh] [--json]
0dai usage                          # local token, task, and USD ledger [status|daily|monthly]
0dai workspace                      # tmux workspace sessions (init|up|status)
0dai runner                         # runner/host architecture and queues [--json]
0dai report                         # privacy-safe project reports (preview|push|status)
0dai compliance                     # SOC2/ISO evidence and ADR audit-trail export
0dai experience                     # structured experience events (list|stats|sync|warnings|dismiss)
0dai receipt                        # session receipt PNG [--last|--active|--session ID]
0dai boneyard                       # weekly digest of worst agent moves [--week YYYY-WW|current]
0dai gh branch-protection           # GitHub branch protection [print|apply|install]
0dai import claude-code-agents      # import .claude/agents/*.md as personas [--dry-run]
0dai auth logout                    # remove credentials
0dai activate code <TEAM-CODE>      # redeem Pro/Team activation code
0dai activate status                # activation and bound-project status
0dai redeem <CODE>                  # redeem a plan upgrade code
0dai upgrade                        # open pricing page (browser or printed URL)

Global flags: --target PATH, --version, --help, --json, --quiet. See 0dai --help for the full surface.

What it does

0dai init and 0dai sync are activation-first. init can complete auth and plan activation in one run: browser/OAuth exchange code via --auth-code, Team/Pro activation code via --code or --activation-code, or the interactive OAuth/device-code prompt. After that it binds the project and sends only allowlisted project metadata (file names + package/build manifests) to the API and generates:

• ai/ — manifests, personas, skills, playbooks, delegation policy
• .claude/ — settings, agents, hooks, rules
• .codex/ — config, agents
• .gemini/ — settings, agents
• .aider/ — config, agents
• AGENTS.md, .mcp.json

Your source code is never sent. Only file names and package/build manifests.

Why 0dai, not just Cursor or Copilot?

Cursor and Copilot are editors. They help inside one coding session. 0dai writes a project layer that Claude Code, Codex, OpenCode, Gemini, and Aider can all read. The point is not another autocomplete box; it is one manifest, one set of agent roles, one task queue, and one health check for the repo.

A fresh 0dai init turns a repo into an AI-ready workspace. It records stack detection, safe project commands, agent preferences, MCP config, and delegation policy under ai/, then writes native files such as AGENTS.md and .mcp.json. Your source stays local; only file names and package/build manifests go to the API.

0dai is useful when work needs more than one model or more than one sitting. You can ask for a backlog item with 0dai run "add password reset tests", check the queue with 0dai swarm status, and continue from the same project facts in another agent CLI. Cursor or Copilot can still be your editor; 0dai keeps the repo-level context and task state outside the editor.

The first five minutes are direct: run 0dai init, run 0dai doctor, then try one backlog task with 0dai run "..." or inspect state with 0dai status. If you only want a local setup, use 0dai init --local; cloud mode adds sync, graph history, and shared task records.

Free-tier examples

On the free tier you get ≈5 backlog tasks/day. Example: in one day you might ask 0dai to split and queue these tasks:

• Write missing tests for the login form.
• Add empty-state copy to the dashboard.
• Check a failing CI log and suggest the smallest code fix.
• Draft a PR checklist from the files changed.
• Summarize today's ai/swarm/done tasks for standup.

Each task can become one or more agent prompts, so the exact count depends on task size. Treat the free tier as enough for a daily cleanup pass; Pro is for larger task queues, graph sync with edges, and session roaming across projects.

Links

• Website: https://0dai.dev
• Docs: https://docs.0dai.dev
• API: https://api.0dai.dev