Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Usage-limit reset messaging reworked with a new gate and reset-scope mapping

Usage-limit reset messages now map limit types to session, weekly, or model-based reset scopes

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

Unclear The finding does not say when the reset note is actually shown to the user or what triggers it, only how it is computed.

What

Claude Code now has internal logic for deciding what to tell you when a usage limit resets. A new helper matches each type of usage limit (five_hour, seven_day, seven_day_opus, seven_day_sonnet, seven_day_overage_included) to a reset scope: session, weekly, or model-specific. A separate function then pulls the actual note text for that scope (note_${scope}) from remote configuration, and normally skips showing the note if the limit hasn't actually been used, unless that behavior (only_if_unused_reset) is overridden.

This logic sits behind a new gate called tengu_wise_bear_copy, whose rollout status hasn't been read yet.

Why

This lets Claude Code give more precise, scope-aware explanations of when a usage limit will reset (for example, distinguishing a per-session five-hour limit from a weekly or model-specific one) rather than one generic message.

Read from
Feature flag
tengu_wise_bear_copy Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.280: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.280. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns [] for tengu_wise_bear_copy, 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 {"note_model":"Use your limit reset to reset it now: `clau.de/reset`","only_if_unused_reset":true} for tengu_wise_bear_copy, 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 {"note_model":"Use your limit reset to reset it now: `clau.de/reset`","note_session":"Use your limit reset to reset it now: `clau.de/reset`","note_weekly":"Use your limit reset to reset it now: `clau.de/reset`","only_if_unused_reset":true} for tengu_wise_bear_copy, 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 [] for tengu_wise_bear_copy, 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 {"note_model":"Use your limit reset to reset it now: `clau.de/reset`","note_session":"Use your limit reset to reset it now: `clau.de/reset`","note_weekly":"Use your limit reset to reset it now: `clau.de/reset`","only_if_unused_reset":true} for tengu_wise_bear_copy, 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 [] for tengu_wise_bear_copy, 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 {"note_model":"Use your limit reset to reset it now: `clau.de/reset`","note_session":"Use your limit reset to reset it now: `clau.de/reset`","note_weekly":"Use your limit reset to reset it now: `clau.de/reset`","only_if_unused_reset":true} for tengu_wise_bear_copy, 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 [] for tengu_wise_bear_copy, 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
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say when the reset note is actually shown to the user or what triggers it, only how it is computed.
The name it cites is new in this buildNew in this build: tengu_wise_bear_copy

See this entry in the whole of v2.1.280 →

Feedback