{"version":"2.1.280","anchor":"usage-limit-reset-messaging-reworked-with-a-new-gate-and-res","canonical_anchor":"usage-limit-reset-messaging-reworked-with-a-new-gate-and-res","heading":"Usage-limit reset messaging reworked with a new gate and reset-scope mapping","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/usage-limit-reset-messaging-reworked-with-a-new-gate-and-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Usage-limit reset messaging reworked with a new gate and reset-scope mapping\n\nUsage-limit reset messages now map limit types to session, weekly, or model-based reset scopes\n\n**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.\n\n**What**\n\nClaude 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.\n\nThis logic sits behind a new gate called `tengu_wise_bear_copy`, whose rollout status hasn't been read yet.\n\n**Why**\n\nThis 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.\n\n- Flag `tengu_wise_bear_copy`: Not enough to say (read for one account on one subscription tier against v2.1.280; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}