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

Gateway spend precheck returns headers for allowed requests too

You'll notice
Useful3 Signal0
Admin Gateway Notable not in their notes

Successful gateway calls now return rate-limit headers, so you can see overage state before being blocked.

anthropic-ratelimit-unified-overage-disabled-reason
What

The admin gateway spend precheck now returns { blocked, headers }, so rate-limit headers reach the client on successful calls and not just on a blocking 429.

Details
  • Previously only the blocking 429 response carried the precheck headers.
  • When the request is allowed and the upstream response is ok, the precheck headers are copied onto that response.
  • This is how clients see overage state, for example anthropic-ratelimit-unified-overage-disabled-reason, on a call that went through.
Evidence

anthropic-ratelimit-unified-overage-disabled-reason

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 →