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

Claude Code v2.1.248 ·

Five analytics events for the weekly limit reset

Five analytics events cover the weekly limit-reset flow.

Nothing to try yet In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
In DevelopmentKind: in v2.1.248,
In DevelopmentSection of the release

Nothing fires unless tengu_nifty_lemur is enabled, off here.

What

The limit-reset flow reports the eligibility check, hitting the limit, the notice being shown, your selection and the claim result. Nothing fires unless the feature is enabled by tengu_nifty_lemur, which is off by default here.

Details
  • Each event carries the experiment arm, subscription tier, availability, low-priority state, config version and the server-supplied tenure, billing path, billing period and extra usage buckets.
Evidence

tengu_juniper_tide_wall

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

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
One source agreesOne thing we can check says the same as this entry.
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