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.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Spend limits are now recognised as rate limits

You'll notice
Useful3 Signal2
Rate Limits

Hitting a service spend limit is now recognised as a usage limit rather than a vague error.

What

A 429 response is treated as a usage-limit condition in more cases: when the body mentions a reached service spend limit, when a response header names a known limit type, or when the error message matches a known type.

Details
  • Triggered by the body text service_spend_limit_reached.
  • Unconditional part of 429 handling.
Evidence

service_spend_limit_reached

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