Changelog
Every template and CLI release, newest first. Filter by product or version.
The workspace template and the CLI are released independently, so a version number names a release of one product, not both. The pages describe the current release; this timeline is where older releases live. Each entry links to its full release notes.
- 2.5.0Current
Template 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
Read Template 2.5.0 notes_archive/after an offer at completion. The agent asks whether to commit and push, or commit only, the records it leaves uncommitted.CLI 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.
Read CLI 2.5.0 notesrecord archivemoves finished records under_archive/, records may sit in group folders, andrecord listandstatusshow your own work first. - 2.4.1
Template 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 notesCLI 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.
Read CLI 2.4.1 notes - 2.4.0
Template 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 notesCLI 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,
Read CLI 2.4.0 notesrecord delete --iddeletes named records, andworktree prunedrops stale associations. - 2.3.0
Template 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 notesCLI 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.
Read CLI 2.3.0 notes - 2.2.0
Template 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 notesCLI Plan folders and exact runs
New plans use a folder with
Read CLI 2.2.0 notesplan.mdand optional assigned details. Plans may be standalone, andrecord order --plan IDselects an exact run. Legacy plans remain readable. - 2.1.0
Template Configurable CLI registry
The workspace adds optional
Read Template 2.1.0 notescli_registryfields forsource,repository, andapi. The installation skill reads those values. A workspace without the setting continues to resolve the public GitHub registry.CLI 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.
Read CLI 2.1.0 notes - 2.0.0
Template 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 notesCLI 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.
Read CLI 2.0.0 notes
Release candidates such as 2.5.0-rc.1 have no notes of their own. The major-version policy explains what history is available.