Source Intelligence
Follow Discord

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.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Spend-cap responses carry unified rate-limit headers

You'll notice
Useful3 Signal0
Rate Limits

Spend-limit blocks now tell you which cap period you hit and when it resets.

What

The spend precheck now picks the most binding cap period that has spend against it and returns anthropic-ratelimit-unified-* headers describing that period.

Details
  • headers cover status, reset, overage utilization, surpassed threshold, retry-after and the period itself
  • the surpassed-threshold header trips at utilization 0.95 and 0.75
  • blocked responses name the offending period and its reset time rather than a generic message
  • failures reading the spend store now surface a fetch_error disabled reason instead of a bare error string
Evidence

anthropic-ratelimit-unified-overage-surpassed-threshold

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.225 →