You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Context UsageArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What
The reporting of context-window usage (how much of the model's available context has been used) has been rewritten around a new shared component that tracks both measured and estimated token counts. It adds a reportAtTurnEnd step that, at the end of a turn, waits briefly for a real measured token count before reporting; if that wait times out, it falls back to an estimate instead.
Why
Previously reported usage numbers could flicker between estimated and measured values or be briefly inaccurate. Waiting for a real count when possible, with a timeout fallback, should make usage indicators (such as a status bar) more stable and accurate without introducing a noticeable delay.
