Context Circuit
Reference

CLI commands

Command groups, concrete examples, and the boundary between mechanics and judgment.

CLI 2.5.0

Invocation

Run every command through the workspace's launcher: sh .context-circuit/cli COMMAND … from the workspace root, sh <root>/.context-circuit/cli COMMAND … from anywhere else, or powershell -NoProfile -ExecutionPolicy Bypass -File <root>/.context-circuit/cli.ps1 COMMAND … in Windows PowerShell or cmd. The launcher runs exactly the pinned version and passes the workspace root. The global flags --workspace PATH and --json may precede the command or follow the full command, but not sit between a group and its subcommand:

sh .context-circuit/cli --json status
sh .context-circuit/cli status --json
sh .context-circuit/cli help
sh .context-circuit/cli help record
sh .context-circuit/cli worktree prepare --help

Command groups

CommandOperations and purpose
version, helpExecutable version and command signatures.
init, status, checkInitialize once, report state, diagnose consistency.
memberadd, band, language, tone, roles, use, list.
workspaceconnect, base, remote for the records repository.
repoconnect, clone, init, base, remote, relate, inspect, fetch.
knowledgeclone, connect, sync, remote, list for borrowed knowledge.
context findSearch by --query or get reconciliation candidates with --repo.
recordcreate, approve, show, list, dependencies, complete, archive, order, delete.
worktreeprepare, list, inspect, move, repair, remove, prune.
agentsettings, configure, setup, dispatch.
template exportWrite the exact blank embedded seed to a new directory.

Read-only examples

sh .context-circuit/cli member list
sh .context-circuit/cli repo inspect --id api
sh .context-circuit/cli context find --query billing
sh .context-circuit/cli record list
sh .context-circuit/cli record list --all --archived
sh .context-circuit/cli record show --id p0001
sh .context-circuit/cli record order --intent i001 --mode waves
sh .context-circuit/cli record order --plan p0001 --mode waves
sh .context-circuit/cli worktree list --repo api

Replace IDs with those in your workspace. Normal output is readable YAML; --json provides structured values. Errors are on stderr and return nonzero status; a flag a command does not take exits 2 with that command's signature.

Mutation is not authorization

Approval and completion commands require the actual corresponding decision. record approve returns planning_recommended; approval, completion, and record archive return commit_recommended for the records and ID files they left uncommitted, and the CLI never stages, commits, or pushes them.

sh .context-circuit/cli member add --id alex --name Alex --band 2 --role maintainer
sh .context-circuit/cli record archive
sh .context-circuit/cli record delete --id p1002
sh .context-circuit/cli record delete --id i101 --id p1003 --confirm
sh .context-circuit/cli worktree prune --repo api

record delete previews the affected records, each with its author, path, and status, and the released IDs without --confirm; deletion requires a request and agreement to the exact preview. --member ID takes one member's records, --id ID (repeatable) takes exactly the named records or a reservation no record holds, and --all takes every record only while the roster lists exactly one member. A refusal returns the preview too, with blocked_by, refused, and, for --id, add_ids, and exits 1. The CLI does not commit, deliver, execute a plan, launch a model, or infer human consent. The pinned command source below contains the complete signatures and refusal behavior.

On this page