v2.7.0
August 13, 2026 · View on GitHub
check now tells you when your quota comes back, not just how much is left.
npm i -g codex-multi-auth
Nothing to migrate. Routing, rotation, storage, and quota math are unchanged — the reset data was already being fetched, this release just shows it.
What's new
✓ Account 1 (...) | live session OK (5h 100%, resets 18:10 | 7d 93%, resets 13:50 on Jul 29)
Times are local, 24-hour. A reset later today shows as HH:MM; past midnight it adds the date.
A few deliberate choices:
- Only
checkshows this. The dashboard, account menu, andforecastare byte-identical to v2.6.1. Those surfaces are already tight on width, so the reset suffix is opt-in andcheckis the only thing that opts in. - Missing or broken reset data just disappears. No timestamp, a zero, a negative, an unparseable date — the percentage still shows and the reset clause is dropped. Nothing about the check depends on it.
- Window labels come from the backend, derived from the reported window length, falling back to
quotawhen it's missing.
Fixed along the way
Quota percentages kept their red/yellow/green colouring. The styling matched an anchored label NN% pattern, and appending , resets ... broke that anchor — which would have quietly greyed out every quota segment and lost the severity colouring entirely.
Also in this release
The product documentation was rewritten against the current architecture, closing the gaps an audit found between the docs and the actual CLI and config (#632).
There's also a new check reference section, which documents something that was never written down: unlike fix, check doesn't skip disabled accounts — it walks every stored account and re-enables one whose token still works.
One note
The date half of the suffix follows your system locale: Jul 29 under en-US, 29 Jul under en-GB, 7月29日 under ja-JP. The HH:MM half is stable. Treat the date as presentation, not something to parse.