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

Spend limits are now recognised as rate limits

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

You'll notice Improvements
JSON All of v2.1.239
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Rate LimitsArea: what it touches
ImprovementsKind: in v2.1.239,
ImprovementsSection of the release
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.

See this entry in the whole of v2.1.239 →

Feedback