{"version":"2.1.239","anchor":"lower-priority-continuation-after-a-session-limit-built-but-","canonical_anchor":"lower-priority-continuation-after-a-session-limit-built-but-","heading":"Lower-priority continuation after a session limit, built but dark","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/lower-priority-continuation-after-a-session-limit-built-but-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Lower-priority continuation after a session limit, built but dark\n\nHitting the 5-hour limit could offer to keep working at reduced priority, but it is off for everyone.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The offer header is `anthropic-ratelimit-unified-slow-offer` and reads either `treatment` or `control`; companion headers `-retry-after`, `-max-wait`, `-budget-utilization` and `-status` carry the retry delay, the ceiling on waiting, how much of the budget is spent, and the current state.\n- There is no local flag for the header side of it, so the server alone decides whether the offer exists; the hidden `\/low-priority` command is gated separately on the client-enabled flag from the config object.\n- 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\".\n- 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.\"\n- 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.\n- A `low_priority_waiting` message kind carries the waiting state alongside those status and wait banners.\n- 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.\n- 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.\n- None of these strings or the `tengu_toasty_breeze` key exist in v2.1.238.\n\n**Evidence**\n\n`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.`\n\n- Area: Usage & Limits\n- Names: `\/low-priority`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}