What changed in 2.9.1

Written on 2026-07-31, 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.

If you only read one thing

Nothing to configure. This is a fix-only release, and both fixes are in the rate-limit readout at the top of the grid. If you run Claude and Codex side by side and that readout has been saying claude usage n/a next to a percentage, this is the release you want.

npx mulmoterminal@latest

The figure beside claude usage n/a was Codex’s, and did not say so

The header could read:

claude usage n/a | 7d 71%

That 71% was Codex’s seven-day window. The note only appears when Claude has no window to show at all, so the number next to it can never be Claude’s — but it was drawn with no mark on it, so the whole line read as “Claude’s 7d is at 71%, only the 5h is missing”. Two different things were wrong at once and the display quietly merged them into one wrong sentence.

The mark that says which tool a set of figures belongs to was only drawn when both tools had numbers. That is exactly the case the note excludes, so in the one situation where the mark was needed it was never there.

How to tell you have it: with both tools running and Claude reporting nothing, the percentage beside the note now carries Codex’s mark. A single tool on the row still gets no mark — a symbol that distinguishes nothing is one more thing to read.

Reference: Feature list

The check no longer decides “API-key billing” before Claude has answered

Claude Code emits its first status line before the session’s first API response, and at that point it carries no rate-limit windows — they do not exist yet. MulmoTerminal took that first, window-less report at face value and concluded the account had no windows, which it reports as API-key billing.

Two things followed from that, both invisible unless you opened the tooltip:

  • the tooltip gave the wrong reason for the missing figures, on accounts that bill normally;
  • the check counted as answered, so a probe that never finished — a trust prompt, a slow start, an expired login, an account already at its limit — was retried on the flat one-hour schedule instead of the backoff meant for a check that got no answer. Every attempt took the same path, so the readout stayed n/a.

A status line that arrives before the first API response is now treated as what it is: not an answer, and not evidence about billing.

How to tell you have it: hover the readout. If your account bills by subscription, it should no longer say the windows are missing because of API-key billing.

Reference: Feature list

Not a bug: Codex has no 5h window

While looking into this we checked every rollout on disk. Current Codex reports a seven-day window only — no five-hour one. That is upstream behaviour, MulmoTerminal files it correctly as 7d, and nothing here changed it. If you were waiting for a Codex 5h figure to appear, it is not coming from this release.

Also in this release

A launch plan for the project was added under plans/. Nothing user-facing.

This site uses Just the Docs, a documentation theme for Jekyll.