{"version":"2.1.310","anchor":"rate-limit-reset-path-now-refreshes-the-five-hour-window-fir","canonical_anchor":"rate-limit-reset-path-now-refreshes-the-five-hour-window-fir","heading":"Five-hour usage limit status is refreshed before it is cleared","tier":"internal","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/rate-limit-reset-path-now-refreshes-the-five-hour-window-fir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Five-hour usage limit status is refreshed before it is cleared\n\nWhen Claude Code clears a five-hour usage limit that had been hit, it now refreshes that limit's status first\n\n**What**\n\nClaude Code tracks a usage limit that resets every five hours. When it clears the record that this limit had been reached, it now refreshes the five-hour limit's status first, and only then reads it.\n\n**Why**\n\nThe five-hour limit state can now be brought up to date before Claude Code clears it, rather than being cleared from whatever it last held.\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"}