Context Circuit CLI changelog
Release history for the independently versioned cli product.
2.5.0 — the launcher, release lines, and the archive
A CLI that is not the pinned one hands off to it, or refuses a migrating or cross-line change. Variant builds install under their own command name. record archive moves finished records under _archive/, records may sit in group folders, and record list and status show your own work first.
2.4.1 — setup splits the IDs, refusals show their preview
The setup step that completes setup makes the ID split and names every file to commit. A refused deletion shows its preview, global flags may follow the command, and worktree preparation reports where it started.
2.4.0 — schema 3, banded members, and deletion by ID
The shared ID file splits into one file per member at schema 3. Every member holds a band, approval recommends planning and committing, record delete --id deletes named records, and worktree prune drops stale associations.
2.3.0 — solo workspaces and record deletion
Initialization can create a solo workspace without a member. Team workspaces report when this machine needs a member selection. Record deletion previews the affected records, requires confirmation, and releases their IDs for reuse.
2.2.0 — plan folders and exact runs
New plans use a folder with plan.md and optional assigned details. Plans may be standalone, and record order --plan ID selects an exact run. Legacy plans remain readable.
2.1.0 — registry-aware installers
Installers accept GitHub or GitLab registry settings through flags or environment variables. GitLab requires a token. Checksum and embedded-version verification remain in place.
2.0.0 — first native executable
The first native CLI provides workspace records, bindings, worktrees, ordering, diagnostics, and dispatch specifications. It begins at 2.0.0 alongside the template; no native CLI 1.x exists.
Coverage
This timeline covers 2.0.0–2.5.0, stable releases only. Release candidates such as 2.5.0-rc.1 have no notes of their own, and each entry is written from its tagged release request. The major-version policy distinguishes guides from release notes and identifies unavailable historical documentation.