Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.277 ·

Usage-limit grace-window messaging made remote-configurable, plus a new wrap-up reminder

The 'Usage limit reached' banner text can now be overridden remotely, and a new gated reminder nudges Claude to wrap up during the grace window

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaRate Limitswhat it touches
KindImprovementsin v2.1.277,
Group of 3 You'll notice No documentation found

The 'Usage limit reached' banner text can now be overridden remotely, and a new gated reminder nudges Claude to wrap up during the grace window

What

  • The pinned "Usage limit reached" notification shown during a grace window now pulls its headline text from a schema-validated remote config (with running/stopped/credits_on keys) instead of hardcoded strings, changes "resets ..." to "limit resets ...", and adds a clickable link to clau.de/wrap-up.
  • This override is controlled by gate tengu_lantern_sconce_copy; if it parses to a valid non-empty value, it replaces the hardcoded messages ("Usage limit reached · wrapping up", "Usage limit reached", "Usage limit reached · brief included wrap-up, then usage credits"), and the parsed value is recorded on the flags diagnostic object.
  • A separate new subsystem can inject a system reminder telling Claude to wrap up work ("finish or checkpoint; don't start subagents or long work") when the session is in a usage-limit grace window. Its message text and mode ("wrap-up" vs "next-steps" vs custom) are configurable, and it's off by default, controlled by gate tengu_lantern_wick_braid.

Why

These changes let Claude Code adjust usage-limit messaging without shipping a new release, and give it a way to actively encourage wrapping up work before a usage-limit grace period ends, rather than just showing a static warning.

Read from
Names in the bundleclau.de/wrap-up
Feature flag
tengu_lantern_sconce_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.277: 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.

tengu_lantern_sconce 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.277: off

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.277. 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 on for tengu_lantern_sconce, 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 doubtWhether the new wording, link, and remote-config behavior are active for any given user depends on the `tengu_lantern_sconce_copy` and…
The name it cites is new in this buildNew in this build: tengu_lantern_sconce_copy

See this entry in the whole of v2.1.277 →

Feedback