Getting Started

AI agents that know your project. One shared brain across Claude Code, Codex, Gemini, Aider, OpenCode, Qoder, and Kimi Code.

0dai generates native configs for supported agent CLIs from a single ai/ directory and keeps their shared context, decisions, and outcomes in sync.

Install

npm install -g @0dai-dev/cli

Authenticate

0dai auth login

Opens a browser prompt. Free accounts are supported — no credit card required.

Activate

0dai activate free

Claims your free activation license. Required before init — even for open-source projects.

Initialize your project

cd your-project
0dai init

This auto-detects your stack (Next.js, FastAPI, Flutter, Go, etc.) 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

Verify

0dai doctor    # check health
0dai detect    # show detected stack
0dai status    # maturity, swarm, session

Keep in sync

0dai sync

Run after editing files in ai/ to regenerate all native configs.

What's next

• Session Roaming — transfer context between agents
• CLI Reference — all commands
• Troubleshooting — fixes for the first errors you hit
• MCP Tools — full reference and plan access
• Delegation Policy — haiku/sonnet/opus routing
• Loop Presets — 8 scheduled autonomous scans

Compare

• Why 0dai — shared repo memory and agent config sync
• Session Roaming — transfer context between agents
• Multi-agent workflow — coordinate parallel agent work
• vs Cursor — repo-owned context for multi-CLI teams
• vs Aider — pair-programming CLI plus shared memory
• vs Claude Code subagents — feature matrix and import adapter

FAQ

Is this just another CLAUDE.md generator?

No. Native configs are the entry point. The value is the living memory, routing, outcomes, and gates around the agents.

Does source code leave the machine?

The free local workflow keeps source local. Product metadata, manifests, and promoted patterns are the cloud boundary.

Why show pricing on the landing page?

The concept is explicit: free stays free, Pro is for the network, Team is for shared operational memory.