8.2.0 — Blueprint steps repair themselves, and closed cells can be reopened

A snapshot as of 8.2.0 (released 2026-10-01). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.

New features

A Blueprints step repairs itself before it stops

When the check at the end of a step failed, a build used to retry three times and then stop, leaving Try again as the only way on — and pressing it repeated the same attempt with the same information. In 8.2.0, with nothing to configure:

On a retry the agent reads the check script itself to see what it asks for (#2812). It never changes the check. The “Turn the actions into features” check also prints the test titles it read and how it counts them.
After three failures in a row, each further attempt is a repair (#2813): the agent sees every earlier failure side by side, works out why every attempt still failed, and fixes that cause. A step now stops after five attempts.
A step that was waiting because another build was working in the same folder resumes by itself when that build stops — finishes, or waits for you (#2814). The same happens when MulmoTerminal restarts.
When the answers to your questions could not be written to their file, the step retries by itself instead of stopping (#2814).

A build that stopped after three attempts on an earlier version picks up again. It still has attempts left, so after upgrading and starting MulmoTerminal it resumes with repairs.

Only one stop is left for you: when Claude Code does not trust the folder yet, since only a person can answer that (Trust a folder for the builds first).

Reopen a closed cell

A cell closed by accident can be reopened from the command palette (#2802).

Open the command palette.
Recently closed cells are listed as “Reopen: <title>”, with when they were closed and their directory. You can search by title or directory.
Pick one and it opens beside the current terminal. An agent resumes its conversation; a shell comes back as a new shell in the same directory (the old screen is gone).

To put it on a key, add terminal-reopen (reopen the terminal closed most recently) to your keymap. It has no key by default, and it can be a header button too. See Keyboard shortcuts. The list lives in this browser only.

Two more shared-app templates

Shared apps gain two shapes (#2804). Ask for what you want in your own words and the agent picks the shape.

A class with a capacity (class-seats) — people signing up see how many seats are left, never who booked. Cancelling is done at your front desk.
A scheduling poll (schedule-poll) — each person gives one answer across the candidate dates and can correct it later. Moving the deadline stops both new answers and corrections.

See Shared apps.

What looks different

When a Blueprints step does stop after using up its attempts, a line above the check’s output says how many times it tried and that Try again sends it back to repairing (#2814).
The notice on a step waiting for another build now says it will resume by itself (#2814).
The icons on the right of the toolbar are grouped (#2801). The command palette and Settings stay at the right end, and buttons that come and go no longer move the others. The new-version notice is now a small icon with a dot instead of a text button; pressing it shows the update command as before.

Under the hood

The document tasks run on chaffjs 0.18 (#2806): a preferred-term finding now names the spelling to use.
The ShapeScript plugin moved to receptron/gui-chat-plugins (gui-chat-plugins#13) and now comes from @gui-chat-plugin/shapescript (#2810). The tools and the view are the same.
Dependencies were updated (#2798).

Nothing here needs doing.