Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Usage-limit wrap-up messages can be tuned per model and now cover the near-limit notice

Usage-limit grace-window text gains per-model and subagent-specific remote settings, and the near-limit notice now counts as a wrap-up note

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

What

The hidden messages Claude Code can send to the model around a usage limit's grace window (a short period near hitting the limit) changed in two ways.

The text can now be set per model through remote settings:

The near-limit notice is handled differently:

  • The near-limit message is now tagged usageLimitNote: "near_limit", where before it carried no tag.
  • The code that finds the last usage-limit note now returns which note it was, instead of only whether it was wrap_up.
  • A near_limit note is now treated like wrap_up: it prevents a reset and can trigger the "release" message. That release step is still controlled by tengu_lantern_wick_braid and related settings such as tengu_lantern_wick_mode.

Nothing has been read about any of these settings, so whether they are active is unknown.

Why

This changes which grace-window messages the model receives when you are close to a usage limit, and lets the wording differ between models and between the main conversation and subagents.

Read from
Feature flag
tengu_lantern_wick_text 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.284: 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_wick_release 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.284: 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.284. 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 null for tengu_lantern_wick_text, 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 "Usage limit reached; a short grace allowance remains, then this turn is cut off without warning. Judge what's left: if it's genuinely only a few steps, finish it properly, then stop and say so without extra polishing. Otherwise don't attempt it all: finish the piece in hand and at most two more like it, then stop. The allowance also pays for any subagents you have running: they don't get this message and will keep going, so it's up to you how to handle them. Either way, end by telling the user their usage limit was reached, what's done and what's left." for tengu_lantern_wick_text, 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 null for tengu_lantern_wick_text, 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 doubtIt is not settled whether a similar per-model setting for resuming after the limit is also new.

See this entry in the whole of v2.1.284 →

Feedback