Context Circuit
Get started

Get started

Create a workspace, connect repositories, and take one change through the circuit.

Template 2.5.0CLI 2.5.0

You work with Context Circuit by talking to your coding agent in ordinary project language. You do not need to choose CLI commands, allocate record IDs, or manage Context Circuit files yourself.

The agent interprets the request, checks the workspace rules, and calls the pinned CLI through the workspace's launcher, sh .context-circuit/cli COMMAND …, when exact bookkeeping or Git mechanics are needed. The launcher runs exactly the version the workspace pins, never a CLI found on PATH. The CLI reports structured facts back to the agent; the agent explains those facts and asks for decisions in project language.

Diagram viewer
100%

Drag to move around. Use the controls to zoom.

Start a new workspace

After creating the template folder and opening it in Cursor, Codex, or Claude Code, say:

Install the Context Circuit CLI version this workspace pins. Then initialize this
workspace as “Acme Billing” for our subscription billing product. Add me as Maya.

The agent resolves the correct binary for its execution environment, verifies it, initializes the shared project identity, adds you to the roster with an allocation band, selects you on this machine, and configures native agent roles. Every workspace has at least one member, so a person working alone is a team of one. It does not expect you to translate that request into commands.

Connect the project

Connect the existing checkout at ../billing-api as `api`, starting from `main`.
It owns billing rules. Then clone our billing web repository as `web` and record
that `web` consumes the `api`.

The agent checks the repositories and asks about missing choices. The CLI records shared repository identities and relationships separately from this machine's checkout paths and base branches.

Take one change through the circuit

Let customers download an invoice as a PDF. Preserve the current authorization
rules and audit trail.

The agent retrieves relevant knowledge and presents the intended outcome with numbered questions. Approving that written outcome records your decision and stops with a recommendation to plan. When you ask for plans — in a later message, or in the same one, as in "I approve it. Create the plans." — it investigates real code and presents them. You then request execution, delivery, and completion as separate decisions.

Diagram viewer
100%

Drag to move around. Use the controls to zoom.

The following pages show the prompts to use and what the agent does with the CLI at each step.

Setup Context Circuit
Create a clean workspace from template 2.5.0 with Tembiter.
Install the CLI
Install the native binary this workspace pins.
Initialize a workspace
Record project identity and add yourself as the first member.
Connect repositories
Give each repository a shared identity and a local checkout.
First Context Circuit workflow
One bounded product change through the full lifecycle.

On this page