Usage-limit reset messages now map limit types to session, weekly, or model-based reset scopes
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.
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.
tengu_wise_bear_copy Not enough to sayNothing 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
The finding does not say when the reset note is actually shown to the user or what triggers it, only how it is computed.
New in this build: tengu_wise_bear_copy