Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

Usage-limit grace now knows which window it belongs to and when it resets

You'll notice
Useful4 Signal3
Usage & Limits

Usage-limit grace now tracks which window you hit and clears itself when that window resets.

What

When 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.

Details
  • 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".
  • Extra-usage status is carried through as "allowed" or "allowed_warning".
  • 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.
  • None of this existed in 2.1.246, which only recorded that grace was active.
Evidence

anthropic-ratelimit-unified-grace-7d-utilization

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.247 →