Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.225 ·

Spend-cap responses carry unified rate-limit headers

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

You'll notice New Features
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Rate LimitsArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
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.

See this entry in the whole of v2.1.225 →

Feedback