What changed in 2.5.1

Written on 2026-07-28, as a snapshot of that day. Behaviour moves; this page does not. For the reference that is kept current, follow the links out of each section.

Windows: the folder picker is the one Explorer uses
Copy the last code block from the latest reply
Tell the issue you are working on it
Opus · ctx 290% is gone
Also in this release

Windows: the folder picker is the one Explorer uses

Nothing to configure. Update and it is there.

The Working-directory picker used to open the legacy “Browse For Folder” tree: no address bar, no box to paste a path into, no Quick access — so reaching a project meant clicking down the hierarchy. It now opens the shell’s own folder dialog, the Explorer-style one, where you can paste C:\work\acme-web straight in.

How to tell you have it: click the folder icon beside WORKING DIRECTORY. If the dialog has an address bar across the top, this is the new one.

If your machine cannot run the interop behind it — a locked-down runtime, a policy that blocks compiling — you get the old dialog instead of an error. Choosing a folder keeps working either way.

The file picker was already the modern dialog; only the folder one had been left behind.

Reference: Configuration guide

Copy the last code block from the latest reply

Nothing to configure. A button in the cell header.

Press it and the last fenced code block of the agent’s most recent reply goes to the clipboard.

Why it exists: selecting that block in the terminal instead drags the leading whitespace of every line along with it, and pasting that into Discord or Slack comes out mangled. This reads the original text out of the agent’s own transcript rather than off the screen, so what you paste is what the agent wrote.

Reference: Feature list

Tell the issue you are working on it

Off by default. Turn it on in ~/.mulmoterminal/config.json:

{ "issueWorkComments": true }

Restart the server, and a cell that is working on an issue says so on the issue — once when it starts, and again when its PR merges:

Working on this in `mulmoterminal5`.

Merged in #983. Work done in `mulmoterminal5`.

The merge comment also closes the issue if it is still open (a PR whose body says Fixes #966 has already been closed by GitHub, so usually there is nothing to do).

Three things worth knowing before you switch it on:

It writes to GitHub under your account, often on an issue somebody else filed. That is why it is off unless asked for.
The directory is the folder name only — mulmoterminal5, never the path above it. It answers “which of my clones”, and these comments land on public issues.
Each comment is written once. Every open tab re-asks on every poll and a reload asks again; an invisible marker in the thread is what keeps that to a single comment. Work the same issue from a second clone and you get a second line, which is the honest answer.
The first restart after switching it on is the noisy one: every cell sitting on a branch that resolves to an open issue says “working on this” at once. Cells on branches whose PR already merged stay quiet.

It needs gh installed and logged in. Without it nothing is written and nothing breaks.

Reference: Telling the issue you are on it

`Opus · ctx 290%` is gone

Nothing to configure.

The context chip divided Opus 5 usage by a 200k window when the real one is 1M — exactly five times too small, which is why the number went past 100%. Opus 5 is in the table now, and a percentage that cannot be real is no longer shown at all.

How to tell you have it: run a long Opus 5 session and watch the ctx chip. It should climb slowly and stay under 100%.