{"version":"2.1.248","anchor":"one-per-week-session-limit-reset-present-but-dark","canonical_anchor":"one-per-week-session-limit-reset-present-but-dark","heading":"One-per-week session limit reset, present but dark","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/one-per-week-session-limit-reset-present-but-dark","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### One-per-week session limit reset, present but dark\n\nYou could clear a five-hour session limit once a week, but the command stays hidden.\n\n**What**\n\nWhen you hit the five-hour session limit, Claude Code can now clear it immediately, once a week, with the usage still counting toward your weekly limit. It surfaces as a hidden `\/limit-reset` command and a \"Reset your session limit now\" row in the rate-limit options menu, and on success the local limit state clears so the interrupted turn can carry on by itself. The whole path is gated on the remote config value `tengu_nifty_lemur`, a server-supplied setting whose compiled fallback is an empty object and which must report `enabled` true, so in this build with no server value the command stays hidden and the menu row never renders.\n\n**Details**\n\n- Applies only to five-hour rate limits, not the weekly limit; a spent variant of the menu row shows disabled once the week's reset is used.\n- Eligibility comes from a `juniper_tide` field on the account status response, reporting whether you are eligible, which experiment arm you are in, how many resets per week you get and when the next one is available, with ineligible reasons including tenure, weekly limit and being in another experiment.\n- Claiming posts `{ program: \"juniper_tide\" }` to `\/api\/organizations\/<uuid>\/reset_rate_limits` with a 25 second timeout.\n- On success the rejected state and the `five_hour` rate-limit record are cleared locally.\n- The same remote config carries `version`, defaulting to 0 and reported with every event, and `autoContinue`, which counts as on unless explicitly set false, so the interrupted turn resumes by default once the feature is switched on.\n- Every user-facing line (menu label, spent, success and failure text) is read per field from the remote config, with built-in defaults as backup: \"Couldn't reset your session limit right now \u00b7 try again in a moment\" for a service failure, and a separate line telling you to run `\/login` and try again when the current login cannot perform the reset.\n- Telemetry covers asked, shown, selected and result events, with menu selection recorded as `tengu_rate_limit_options_menu_select_juniper_tide`.\n\n**Evidence**\n\n`Reset your session limit now and keep working; once a week, still counts toward your weekly limit`, `tengu_rate_limit_options_menu_select_juniper_tide`, `Session limit reset \u00b7 next reset available {date} \u00b7 your weekly limit still applies`, `s5n = \"tengu_nifty_lemur\"`, `Couldn't reset your session limit with this login \\xB7 run \/login, then try again`\n\n- Area: Usage & Limits\n- Names: `\/limit-reset`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}