Context Circuit

Workspace template changelog

Release history for the independently versioned template product.

2.5.0 — the launcher and the archive

Every workspace carries a launcher that runs exactly the pinned CLI. Records may sit in group folders and are archived under _archive/ after an offer at completion. The agent asks whether to commit and push, or commit only, the records it leaves uncommitted.

Read template 2.5.0

2.4.1 — setup completes the ID split

The setup step that completes setup makes the ID split and names every file to commit. A refused deletion shows its preview, and a prepared worktree says where it started.

Read template 2.4.1

2.4.0 — schema 3, banded members, and planning on request

One ID file per member at schema 3, with one person upgrading first. Every member holds a band, approval stops with a recommendation to plan, records can be deleted by ID, and worktrees from an earlier plan with the same number are refused.

Read template 2.4.0

2.3.0 — solo workspaces and controlled deletion

The template supports an empty roster, asks for member selection before team changes, and requires a preview and agreement before deleting records. Its quick-start command uses the published version tag.

Read template 2.3.0

2.2.0 — direct planning and plan details

A person can request a grounded plan without an intent. New plans use folders, with linked detail files assigned for shared or repository-specific reading. Execution still needs a separate request.

Read template 2.2.0

2.1.0 — configurable CLI registry

The workspace adds optional cli_registry fields for source, repository, and api. The installation skill reads those values. A workspace without the setting continues to resolve the public GitHub registry.

Read template 2.1.0

2.0.0 — the v2 workspace

The stable v2 release establishes the native CLI boundary, explicit human decisions, durable knowledge, worktree coordination, and independent product releases.

Read template 2.0.0

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.

On this page