You could clear a five-hour session limit once a week, but the command stays hidden.
A hidden /limit-reset command and menu row exist behind tengu_nifty_lemur, which has no compiled value.
What's wrong with this entry?
When 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.
- 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.
- Eligibility comes from a
juniper_tidefield 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. - Claiming posts
{ program: "juniper_tide" }to/api/organizations/<uuid>/reset_rate_limitswith a 25 second timeout. - On success the rejected state and the
five_hourrate-limit record are cleared locally. - The same remote config carries
version, defaulting to 0 and reported with every event, andautoContinue, which counts as on unless explicitly set false, so the interrupted turn resumes by default once the feature is switched on. - 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 · try again in a moment" for a service failure, and a separate line telling you to run
/loginand try again when the current login cannot perform the reset. - Telemetry covers asked, shown, selected and result events, with menu selection recorded as
tengu_rate_limit_options_menu_select_juniper_tide.
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 · next reset available {date} · your weekly limit still applies, s5n = "tengu_nifty_lemur", Couldn't reset your session limit with this login \xB7 run /login, then try again
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 limit usage
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention limit usage
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention limit usage