Requests can be tagged as running against a slower usage budget, with a matching reset header recognised.
What's wrong with this entry?
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.
- The header is added by the shared request layer when the URL path ends in
/v1/messagesand the phase check passes. - Nothing in the build forces the phase active, so whether you ever see this is decided elsewhere.
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.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit