[nowrap]

Two things visible in one screenshot of the details fly-out: Claude paused on a rate limit, and two Codex rows both reading Codex · Woche, one of them stuck at 0 %.

The usage endpoint was asked 40 times an hour

refreshSeconds was the only thing deciding how often a provider was reached. The windows being watched are 5 hours and 7 days wide, and the tray is not the only client spending the account's request quota — so most of those requests could not learn anything, and the 429 they earned cost the display a quarter of an hour at a time.

A provider now states its own floor (IUsageProvider.MinInterval) and PollScheduler enforces it on top of the backoff — whichever pause is longer wins. Claude's floor is claude.minIntervalSeconds, 300 s by default and exposed in the settings dialog; Codex keeps zero, being a local process with nothing to spend. Reset() clears the spacing along with the backoff, so the menu's refresh command still reaches everything at once.

Two weekly windows that read alike

The prolite plan reports a second bucket, codex_bengalfox, carrying limitName: "GPT-5.3-Codex-Spark" — a per-model weekly limit, the exact analogue of claude.weekly_scoped.fable. AddWindows ignored the name, so both rows rendered from the window alone and the model's limit — 0 % until that model runs — looked like the account's limit had stopped filling.

The named bucket now reads Week · GPT-5.3-Codex-Spark, the shape Claude's per-model window already uses. The service prefix is dropped there on purpose: Codex · Week · GPT-5.3-Codex-Spark measures 248 px against a 222 px label column, so the ellipsis would have eaten the only part that tells the rows apart. Only the account-wide window keeps the active dot — whether a model is the one currently running is not something the server says.

Verification

• 235 unit tests pass, 13 of them new: minimum spacing (skipped cycles are not failures, an explicit refresh beats the floor, the floor survives a reset because it is configuration, a longer backoff still wins) and the Codex labelling (named, unnamed fallback, active only on the account-wide window).
• --once against the live account confirms the new bucket parses as codex.codex_bengalfox.primary at 0 % without the active marker.

🤖 Generated with Claude Code