Gateway-authenticated sessions now get the same rate-limit tracking and 429 handling as subscription ones.
What's wrong with this entry?
Sessions authenticating through the gateway get the same unified rate-limit handling that subscription sessions already had.
- the guarding predicate changed from "caller says so, or the subscription check passes" to additionally accepting a
gatewayauth source - covers unified rate-limit header parsing, 429 handling and the background usage probe
anthropic-ratelimit-unified-overage-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