{"version":"2.1.247","anchor":"usage-limit-grace-now-knows-which-window-it-belongs-to-and-w","canonical_anchor":"usage-limit-grace-now-knows-which-window-it-belongs-to-and-w","heading":"Usage-limit grace now knows which window it belongs to and when it resets","tier":"notice","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/usage-limit-grace-now-knows-which-window-it-belongs-to-and-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Usage-limit grace now knows which window it belongs to and when it resets\n\nUsage-limit grace now tracks which window you hit and clears itself when that window resets.\n\n**What**\n\nWhen you hit a usage limit and are given grace to finish what you are doing, Claude Code now tracks whether the grace belongs to the 5-hour or the 7-day window, when that window resets, and whether extra usage is allowed or allowed with a warning. The grace state clears itself once the window has passed instead of staying latched.\n\n**Details**\n\n- The window is picked by comparing the 5-hour and 7-day reset timestamps returned by the server, and recorded as `\"seven_day\"` or `\"five_hour\"`.\n- Extra-usage status is carried through as `\"allowed\"` or `\"allowed_warning\"`.\n- A single accessor now returns the limit type, reset time and extra-usage status together, and a companion call expires the latch after the reset.\n- None of this existed in 2.1.246, which only recorded that grace was active.\n\n**Evidence**\n\n`anthropic-ratelimit-unified-grace-7d-utilization`\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}