Your coding agent can only touch what you opened for it

CommitCycle gives each agent a grant bound to one task and one branch that expires on its own. The paths that would hurt carry an owner and a risk level, moving a wall takes one approval with a reason, and every task closes with a record of what it declared versus what it touched. These pages explain how, and just as deliberately, what it will not do.

What is CC?How the three layers work

With an invite you can open a board, connect your editor with one line and have your agent propose a zone map — see the quickstart. Signup is closed while this is small; the product runs, the door is narrow, and those are different facts.

Enforcement now ships too: the plugin installs from the marketplace inside Claude Code, and the CLI installs from npm — what each one does, including which of the two is the wall. It stays a deliberate install rather than an automatic one, because a repository carrying hook configuration with no binary behind it looks protected and blocks nothing. Until you install it, a connected repository is documented rather than guarded, and the audit record says so in its own fields rather than rounding the silence up to “verified”.

These docs are written alongside the build, in the open: pages that exist describe what is real, and pages that are pending say so and name the task that will fill them.

Start here

What CommitCycle is — zones, the board, the gate — then the quickstart and how to install it.

Concepts

Memory and governance modes, zones, the four-field task spec, the three enforcement layers and just-in-time grants.

Reference

The CLI, the MCP tools, what lives in .zones/, zones.yml, the board API and the glossary the product’s vocabulary comes from.

Operations

The closing gate, two accounts on one machine, two sessions at once, and what a block means when you hit one mid-task.