12.0.1 — A path right after a full-width colon is a link

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

Nothing to configure. Upgrade and the fix is there:

npx mulmoterminal@latest

New features

None in this release.

What looks different

A path right after ： is linked on its own

A file path printed in terminal output becomes a link you can click (Clickable file paths). When an agent wrote Japanese and put the path straight after a full-width colon, with no space —

できたこと：D:\Users\me\work\notes.md の該当行に追記しました。

— the link went wrong (#3269, for #3268):

• a / path such as できたこと：src/a.md was linked together with the Japanese before it, so a click asked for a file that does not exist;
• a Windows drive path such as できたこと：D:\x\a.md was not linked at all.

A half-width : followed by a space was always fine. Now the full-width ：；，！？ end a path the way 、 and 。 already did, so only the path is underlined.

One side effect: a file whose name itself contains one of those five characters is now cut at that character — the same trade already made for 、, 。 and full-width brackets.

How to tell you have the fix: print a line like the one above in a cell (for example echo 'できたこと：docs/plan.md を見た' in a directory that has docs/plan.md) and hover the path. From 12.0.1 only docs/plan.md is underlined; before, the underline started at で.

Under the hood

The two routes that answer the Files pane’s reads and changes now share one body for the “is this path inside the folder” check (#3267). The answers are the same as before — a folder that has gone away is still “not found”, and a path that climbs out of it is still refused. Nothing to do.