Changelog

What you can do with mcue this week that you couldn't last week. Published every Friday. Each entry is one capability, named by the part of mcue it lives in, with the release that carries it. A week with nothing to report gets one line saying so — that is information too. Release-by-release detail, including fixes, lives in the repository's CHANGELOG.md.

Fri 2 Oct 2026

Read any past checkpoint — mcue history <project-id> --show <file> prints one checkpoint verbatim, and the checkpoint_read MCP tool does the same for agents, locally and on hosted MCP. Until now only the latest checkpoint could be read; once a later closeout superseded one, what it recorded was out of reach. Text history rows now start with the file name --show takes. v0.21.0, Hub

Plans can gain a step — mcue plan update --add-step "<text>" [--after <n>] inserts an open step into an existing plan; later steps renumber and the current step stays put. closeout --plan-add-step, and plan_add_step on the local and hosted closeout tools, adds one in the same write as the checkpoint. Previously new work could only be recorded as a plan note. v0.21.0, Hub

A focused index — mcue index --focus, and focus on the index MCP read, leaves out stale lanes and ends each project with how many it omitted, so the lanes in play on a large project fit on one screen. Opt-in: the default still shows every lane. v0.21.0, Hub

Multi-lane projects read correctly — A project's header now follows its default lane instead of whichever lane closed out last, so it no longer mixes one lane's objective with another's resume pointer; index labels the next action with its lane ([trunk] …). Project and lane IDs print in full, so any ID shown can be passed to resume. The expanded resume packet cuts a long outcome at a word and says how to read the rest, rather than stopping mid-sentence. Locally and on the Hub. v0.21.0, Hub

Concurrent reads don't queue — review, resume, index, history and the mcue serve read tools now share the local journal lock with other readers, so several agents reading at once no longer wait on each other or time out. Writers are still excluded. v0.20.1

Safer Hub recovery — Retrying a pending closeout that the Hub had already recorded now clears it as "already recorded" instead of leaving it as unknown. A backup download interrupted by a Hub error aborts instead of saving a partial file that looked complete. Signing out lands on the sign-in page instead of a 404. Hub

Fri 25 Sep 2026

Hub agent access — An AI app you connect can now save to your own projects from its first closeout, and create a new project from the chat, with no grant to set first. Previously a new client started read-only and its first save was refused until you elevated it on the dashboard. Clients already connected to your own projects move to write too, except where you set access explicitly. Account access and each project's MCP client grants now offer Restrict to read and Revoke, and a restricted client's refused write still names the client and where to change it. On a lane shared with you, the agent choice when you join now starts on write wherever the owner's share allows it; pick read to keep your agents read-only. Hub

Closeouts survive interruption — A closeout from the CLI or the local MCP server now writes its complete set of changes to a private local journal before it replaces any file. If the process dies part-way, the next governed read finishes applying it. If a file it touched was edited in the meantime, recovery stops and keeps the original intent rather than guessing. v0.19.0

Hosted closeouts you can retry — A hosted write no longer answers "hosted write failed; try again" for every problem. The Hub now says whether it was accepted, refused and why, in conflict, transient, or unknown. Every hosted closeout, lane creation and lane close carries a request ID the caller keeps, so a retry after a lost response returns the original result instead of writing twice. In the Hub, the closeout form keeps your draft until the Hub confirms it, and the lane page gains a recovery panel for pending attempts: retry, download what was submitted, or discard. Agents on hosted MCP must now send the request ID; one that omits it is refused before anything is written. v0.19.0, Hub

Projects of any size — Accumulated history is no longer a closeout limit. Incremental sync handles projects past the 500-file / 5 MiB budgets of a first publish, and the Hub validates each changed file instead of hashing the whole project. mcue publish --bounded and mcue clone --bounded move projects up to 100,000 files and 1 GiB in chunks, and the Hub offers a backup download you can verify with mcue hub unpack. v0.19.0, Hub

Indexed sync — Opt-in. mcue sync migrate <project-id> moves a clean replica onto indexed sync: each queued write keeps its exact bytes and IDs across lost responses and offline edits, and a conflict stops instead of silently rebasing. When the Hub refuses a queued write because another writer's accepted closeout changed the same state, mcue sync resolve <project-id> merges the derived state and submits one successor; anything it cannot merge safely stays flagged with nothing changed. Every writer to a migrated replica needs v0.19.0 or later; use v0.20.0, since on v0.19.0 such a refusal froze the replica. v0.19.0, v0.20.0

Hub activity history — Activity now pages through your complete history, newest first, with project, lane and action filters. It previously showed a snapshot capped at 50 projects and 100 operations each. A multi-file closeout appears as one act, grouped by the batch the Hub accepted it in. Hub

Hub project page — A project page is now a lane index: one row per active lane with its next action, pointer and signals. The acceptance record, activity, client grants and files fold under Manage project. Ask Hub moves to the top bar, and labels that carry meaning are larger and meet contrast. Hub

Hub onboarding for agents — The first-run dashboard and the onboarding page now show the hosted MCP endpoint to paste into your AI app, ahead of the CLI steps, so starting from the browser no longer needs a trip to the docs. Hub

Fri 18 Sep 2026

mcue observe and hosted drift — A hosted agent reading a project through the Hub cannot see your repository, so until now it could not tell whether the work had moved since the last accepted checkpoint. mcue observe <project-id> --upload, run on the host that owns the repository, collects branch, HEAD and Git status against the Hub-accepted checkpoints and uploads them as evidence. The hosted drift and resume reads compare the latest evidence with each accepted perspective; evidence older than fifteen minutes reads unknown rather than pretending. A hosted closeout can name a fresh observation as its Git baseline. Collection is one-shot with no background process; a periodic job on your machine gives it a cadence. Coverage is Git state, not file contents. v0.18.0

Agents contract — Every agents-snippet variant now opens with a mandatory five-step recovery procedure: find the project, discover its lanes, select the lane by the operator's current request, read its bounded packet, only then open the code. The agent states which lane it is using and checks alignment before proposing a closeout. Local and Hub state are treated as separate sources, so a warning on one is never silently resolved by a clean read on the other. v0.15.0

Lane objectives — mcue review and mcue index --expand-lanes print each lane's objective, and the MCP index tool gains expand_lanes, so an agent can pick a lane by what it is for without a call per lane. v0.15.0

Checkpoint history — A new checkpoint_history MCP read and mcue history --json return a project's checkpoints as bounded JSON header rows, newest first, with lane to restrict and total to say how many matched. The CLI, the local server and the Hub return the same shape. v0.16.0

Agents over MCP — The contract explains a stale tool list: a tool list is taken when a conversation starts, a release can add a tool that conversation will never see, and the server's handshake version is the contract it serves. It also treats a refused hosted write as a designed state: the agent relays the Hub's elevation guidance, stops writing, and does not retry through another tool until you have acted. v0.16.1, v0.16.2

mcue lane update — Change a lane's objective, name, or work tree after creation. The objective is the scope statement agents select a lane by, so when ownership or scope changes the stored objective changes with it. Objective and name reach the Hub on the next sync; --root stays machine-local. v0.17.0

Hub write access — A hosted write refused for want of a grant now names the client and the page to elevate it on. Account access lists every client that has read your projects, by its registered name, with a one-click Elevate to write. Previously a freshly connected agent was invisible there and elevation meant typing an opaque client ID. Hub

Hub shared lanes — Agents a member connects can now work on a lane shared with them. The owner sets the ceiling when minting the share, with Agents may write on write shares; the member decides for their own agents when joining, and can change it later under Shared with you on Connections. Agent write is off unless both have said yes. Hub

Hub continuity graphs — Project and lane pages show accepted closeouts across their history, with density buckets, hover and keyboard tooltips, and a table view. Project pages also show each lane's share of the record. Project topology in the sidebar opens a portfolio of projects and active lanes with links into their history; pan and zoom it or switch to its list view. Select history marks to inspect stored checkpoint packets, and colour buckets by confidence, quality, or plan step without hiding non-explicit records. Read the guide. Hub

Hub lane page and activity — The lane page is now the packet: the next move split per actor, the resume pointer as typed chips into commits, files, and plan steps, blockers and drift beneath, and a plan stepper. Copy packet stays byte-identical to the CLI. The activity feed shows what the Hub accepted, in words, one row per closeout, plan update, or lane change, with the raw file operations folded underneath. Hub

Getting started — One page takes a first-time user from saving an existing AI conversation, through a fresh chat that carries on, to a plan worked step by step and the Hub. Read the tutorial. Docs

Fri 11 Sep 2026

Agents over MCP — An agent connected to a mcue MCP server now receives the access contract in the server handshake, and can re-read it at mcue://agents. A client that has never seen mcue learns the vocabulary — project, lane, checkpoint, perspective, signals — and the read-first, closeout-at-ship rules before its first tool call. Previously the MCP surface described itself only through one-line tool descriptions. mcue agents-snippet --mcp emits the same text for hand placement. v0.14.0

mcue init — The project id is validated before anything is written, and the error tells you what to type instead. mcue init CompIQ used to scaffold a project that closed out locally and then failed at publish; it is now refused with the runnable line mcue init compiq --name "CompIQ". --name is optional and defaults to the id. The MCP init tool shares the same check. v0.14.1