Hitting the 5-hour limit could offer to keep working at reduced priority, but it is off for everyone.
A whole lower-priority subsystem with a hidden /low-priority command needs a server arm and config with enabled true.
What's wrong with this entry?
When you hit the 5-hour usage limit, Claude Code can offer to keep working at reduced priority against your weekly allowance instead of making you wait, with a hidden /low-priority command, an entry on the usage-limit dialog, a waiting state, and its own retry and stop-reason accounting. Nothing appears unless the server both puts your account in the treatment arm through a response header and ships a config object named tengu_toasty_breeze with enabled set to true. That config defaults to empty, so enabled is false and the whole subsystem is off for everyone in this build.
- The offer header is
anthropic-ratelimit-unified-slow-offerand reads eithertreatmentorcontrol; companion headers-retry-after,-max-wait,-budget-utilizationand-statuscarry the retry delay, the ceiling on waiting, how much of the budget is spent, and the current state. - There is no local flag for the header side of it, so the server alone decides whether the offer exists; the hidden
/low-prioritycommand is gated separately on the client-enabled flag from the config object. - The command is registered hidden, so it never shows in the command list, and its description reads "Continue now at lower priority after reaching your session limit; run again to stop".
- Choosing the menu entry records a selection event, and when the server has not made the offer the menu answers "Lower-priority mode isn't available right now."
- Four pieces of copy come from the same config and can be replaced by the server: the menu label, a notice line, a status line, and the banner shown while waiting.
- A
low_priority_waitingmessage kind carries the waiting state alongside those status and wait banners. - 429 responses that report a busy slot are retried with jitter, and the mode records why it stopped: weekly allowance exhausted, budget, maximum wait exceeded, wall clock and others.
- Six telemetry events cover the flow: offer capable, offer shown, accepted, request, wait, ended; API-error telemetry gained a marker for requests made on the low-priority path.
- None of these strings or the
tengu_toasty_breezekey exist in v2.1.238.
Continue now at lower priority, You've used this week's lower-priority allowance, /${wlr} to continue now at lower priority (counts toward your weekly limit), Lower-priority mode isn't available right now.
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