{"version":"2.1.310","anchor":"usage-limits-parser-now-takes-a-previous-snapshot","canonical_anchor":"usage-limits-parser-now-takes-a-previous-snapshot","heading":"Usage limit readings now combine with the previous values","tier":"internal","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/usage-limits-parser-now-takes-a-previous-snapshot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Usage limit readings now combine with the previous values\n\nClaude Code now merges each new usage-limit reading with the previous one for the five-hour, seven-day and included overage windows\n\n**Unclear.** It is not clear how the old and new values are merged, so whether figures look smoother or can show stale values is unknown.\n\n**What**\n\nClaude Code keeps track of how much of your usage limits you have used. When it reads new usage figures, it now merges each one with the previous reading for the same window, rather than taking each reading on its own. The windows are:\n\n- The five-hour window.\n\n- The seven-day window.\n\n- The seven-day window with included overage.\n\n**Why**\n\nThis may change how your usage figures look between updates. A window missing from a new reading may now keep showing its previous value.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}