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

Requests can now be marked as running against a slow usage budget

Under the hood
Useful2 Signal4
Usage & Limits

Requests can be tagged as running against a slower usage budget, with a matching reset header recognised.

What

Requests to the messages endpoint can carry a new header, anthropic-usage-limit: slow, set when an internal usage-limit phase reports as active. The build also recognises a matching response header naming when a slow budget resets. The previous build had neither, only an "extended" value.

Details
  • The header is added by the shared request layer when the URL path ends in /v1/messages and the phase check passes.
  • Nothing in the build forces the phase active, so whether you ever see this is decided elsewhere.
Evidence

anthropic-ratelimit-unified-slow-budget-reset

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 →