12.1.1 — A Codex cell keeps reporting when it is working

A snapshot as of 12.1.1 (released 2026-11-06). 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 Codex cell’s working dot and finished notice no longer go quiet

A cell running Codex shows a working dot while Codex is busy and announces when a turn ends (the finished sound and, if you set it up, a push to your phone). For that, MulmoTerminal has to find the conversation file Codex writes, and in two situations it never did, so the cell looked idle forever:

The first prompt came more than thirty minutes after the cell opened. Codex only writes its file when you send the first prompt, and the search for it gave up after thirty minutes. It now keeps looking for as long as the cell is open (#3284, for #3282).
The server restarted while such a cell was running. After a restart MulmoTerminal reconnects to the Codex still running in the cell, but without the record of which file was its own, it could not find it again. It now asks the running Codex which conversation file it has open, and takes it only when there is exactly one, so it never picks another cell’s conversation (#3285, for #3283). Turns that finished before the restart are not announced again. This works on macOS and Linux; it needs lsof, which both have.

A cell already in this state is picked up on the first server start after the upgrade, as long as its Codex is still running.

How to tell you have the fix: in a Codex cell that had stopped showing activity, send a prompt. From 12.1.1 the dot turns to working while Codex answers, and you get the finished notice when it ends. More: Mixing agents in one grid.

Under the hood

Nothing else in this release.