Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

One-per-week session limit reset, present but dark

You could clear a five-hour session limit once a week, but the command stays hidden.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
In DevelopmentKind: in v2.1.248,
What probably matters to youSection of the release

A hidden /limit-reset command and menu row exist behind tengu_nifty_lemur, which has no compiled value.

What

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.

Details
  • 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_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.
  • Claiming posts { program: "juniper_tide" } to /api/organizations/<uuid>/reset_rate_limits with a 25 second timeout.
  • On success the rejected state and the five_hour rate-limit record are cleared locally.
  • 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.
  • 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 /login and 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.
Evidence

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.

Read from
Names in the bundle/limit-reset
What has happened since
Flag reading moved The flag server now returns {"enabled":false,"version":0} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"autoContinue":true,"enabled":true,"label":"Reset your session limit now","noticeLine":"/limit-reset to reset your session limit now · uses weekly limit · 1/week","spentLine":"Weekly reset used · available again {date}","successLine":"Session limit reset · next reset available {date} · your weekly limit still applies","unavailableLine":"Couldn't reset your session limit right now · try again in a moment","version":1} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"enabled":false,"version":0} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"autoContinue":true,"enabled":true,"label":"Reset your session limit now","noticeLine":"/limit-reset to reset your session limit now · uses weekly limit · 1/week","spentLine":"Weekly reset used · available again {date}","successLine":"Session limit reset · next reset available {date} · your weekly limit still applies","unavailableLine":"Couldn't reset your session limit right now · try again in a moment","version":1} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"enabled":false,"version":0} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"autoContinue":true,"enabled":true,"label":"Reset your session limit now","noticeLine":"/limit-reset to reset your session limit now · uses weekly limit · 1/week","spentLine":"Weekly reset used · available again {date}","successLine":"Session limit reset · next reset available {date} · your weekly limit still applies","unavailableLine":"Couldn't reset your session limit right now · try again in a moment","version":1} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"enabled":false,"version":0} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"autoContinue":true,"enabled":true,"label":"Reset your session limit now","noticeLine":"/limit-reset to reset your session limit now · uses weekly limit · 1/week","spentLine":"Weekly reset used · available again {date}","successLine":"Session limit reset · next reset available {date} · your weekly limit still applies","unavailableLine":"Couldn't reset your session limit right now · try again in a moment","version":1} for tengu_nifty_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's release notes agreeFixed the recommended Console sign-in in /login failing with an OAuth error before showing a sign-in URL on machines where it can't be used…
The name it cites is new in this buildNew in this build: tengu_nifty_lemur

See this entry in the whole of v2.1.248 →

Feedback