0-CODE

Version: v2.0.2

An autonomous development cycle for Claude Code, Codex and OpenCode, integrated into an existing project. One cycle prompt can contain research, implementation, repairs, audits and release work.

English · 中文 · Español · Português · Русский · 日本語 · 한국어 · Français · Deutsch · हिन्दी · العربية

Integrate with your agent

In your project's agent session, ask: “Integrate 0-CODE from https://github.com/0-SOFT/0-CODE; follow its INTEGRATE.md.” Use a public source checkout outside the target project, optionally at a chosen release tag. The same short template handles upgrade and uninstall for all three engines.

The agent scans project documents, tools, MCP and check commands, resolves genuine ambiguities, previews changes, installs, runs doctor and commits in a separate branch. Existing project tools take precedence. Manual quick start.

What is installed

Framework code, configuration, schemas, modules and templates live in .0-code/. Engines receive only their required native hooks, instructions, compatible tool entries and the OpenCode guard plugin. Existing code and documents are preserved; collisions and changed owned files are reported before writes. Runtime files and backups live in ignored .0-code/run/.

The single configuration reference is PROJECT_SETTINGS. Choose default documents, override individual roles, or map all roles to existing project conventions. The state remains a machine-readable document. Human documents use the configured language; agent instructions stay in English.

Model, reasoning effort and login belong to the owner. Settings resolve as explicit flags > environment > project configuration > native engine preferences. Unspecified model and effort are inherited; authentication is never copied. See engine settings.

The public tool catalog contains five default MCP servers: context7, playwright, chrome-devtools, sequential-thinking and memory. They need npm packages at or above the tested SemVer minimum, with the correct package name and entry point; preserve valid newer packages. They require no external API key; browser tools also need an available browser. Registration and a green doctor do not prove a live connection. Private skill, agent, command and rule bodies are excluded. Optional account examples in the MCP manifest stay off until explicitly configured and authorized.

Tools default to one independent installation per user, shared across that user's projects. Reinstalling the same selection changes nothing. Use project scope to pin a different selection in a project. Project uninstall leaves machine tools; uninstall-tools removes the separately owned machine installation and restores its original native settings. Authentication is never copied. See configuration and prerequisites.

Work and maintain

From an installed project:

node .0-code/tools/0code.mjs doctor --json
node .0-code/tools/0code.mjs start <cycle-prompt> --max 60
node /path/to/new-source/tools/0code.mjs upgrade --project . --dry-run
node .0-code/tools/0code.mjs uninstall --dry-run

Fill the single .0-code/templates/cycle.md template. start atomically sets the state and prints the chosen driver command. Restart Claude to load new hooks; Codex and OpenCode use the external supervisor. One folder has one active cycle. Iteration and spending limits are opt-in; spending limits require supervisor cost data. Register long jobs in state instead of polling with sleeps.

The public checkout supports new installations and upgrades of the .0-code/ layout. Automatic migration of old root-based 1.x installations is unavailable without config/legacy-installations.json, which is excluded from the public tree. Use migrate --dry-run, then migrate, only with a source containing the published ownership evidence. Only byte-proven framework files and exact owned blocks are removed; documents stay in place and runtime is archived or moved with backups. Finish a live old cycle first; without evidence, preserve the old files and review their ownership before changing them.

Engine settings explain precedence and personal login. Claude setup, development guide, and security explain operation and validation. In the source checkout, run node tests/run.mjs --coverage-min=80 and bash tests/smoke.sh; local results are evidence, and CI availability is separate.