CLI commands
Use structured operations for facts and files; leave interpretation to the agent.
Read the available surface
sh .context-circuit/cli version
sh .context-circuit/cli help
sh .context-circuit/cli help worktree
sh .context-circuit/cli --json statusEvery command runs through the workspace's launcher, which runs the pinned version and passes the workspace root. The global flags --workspace PATH and --json may precede the command or follow the full command, as in sh .context-circuit/cli member list --json; they do not go between a group and its subcommand. Normal output is readable YAML; --json returns structured values. Errors go to stderr with a nonzero exit status. A fully resolved command accepts --help; a flag it does not take is named, followed by its signature and the help topic to read, with exit status 2. Groups need a subcommand for flag help.
What commands can do
The CLI initializes workspace files, manages members and bindings, retrieves catalog entries, creates records, records decisions already made, derives dependency order, previews requested record deletion, prepares worktrees, and produces diagnostics or dispatch specifications.
Every workspace has a roster, and every member a band. init requires a first member and suggests band 1, and member add requires --band; without it, it names the next free band. Band 0 is a band like any other and starts at i001 and p0001, and a band is never cleared. Until the roster lists a member, every member holds a band, and this machine has selected one, every changing command is refused except init, member add, member use, and member band. status reports identity_required, band_required with suggested bands, and next_band.
A member may carry free-text roles, set with member add --role, init --member-role, or member roles, and cleared with member roles --clear. Roles are shown with the roster and decide nothing.
status opens with my_work: your intents awaiting approval, approved intents without plans, open plans, and the count of finished records not archived. record list lists your own records; --member ID lists another member's, --all every record, and --archived adds archived ones. record archive moves your finished records under _archive/, or exactly the records named with repeatable --id.
New plans use folders with plan.md; record order --plan ID selects an exact run. record approve returns planning_recommended, and approval, completion, and archiving return commit_recommended for the records and ID files they left uncommitted. record delete --member ID previews one member's records, --id ID (repeatable) previews exactly the named records or a reservation no record holds, and --all previews every record only while the roster lists exactly one member. Nothing is deleted until the requested preview is confirmed with --confirm; a refusal still shows the preview.
It does not call a model, execute a plan, run application setup, commit, push, merge, deploy, or start an independent review.
Read the command reference for each group and concrete examples.