A gateway spend block no longer scrambles the rate-limit usage indicator you see.
What's wrong with this entry?
A 429 injected by the gateway, for example a spend block, no longer overwrites the displayed Anthropic rate-limit state.
- Rate-limit status tracking returns early when the provider is the gateway and the 429 response lacks the unified status header.
anthropic-ratelimit-unified-status
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.
-
v2.1.234
Rate-limit prompts resolve model aliases to the model that actually answers
Both mention rate limit
-
v2.1.234
Quota rejections feed a new auto-resume controller
Both mention rate limit
-
v2.1.239
Spend and rate limit notices say when the limit resets
Both mention rate limit