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.282 ·

Usage-limit grace signal now tracks the most recent response

The signal for being in a usage-limit grace window now follows the latest main or subagent response and clears when no grace use is reported

Under the hood Internal Changes
JSON All of v2.1.282
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
Internal ChangesKind: in v2.1.282,
Internal ChangesSection of the release

Unclear Only the description of the signal changed visibly, so it is not confirmed that the code computing it changed the same way.

What

Claude Code keeps an internal signal for whether your account is in a grace window, a short allowance past a usage limit. Before, the signal stayed set once it had been seen on a response to a request that asked for extended usage.

Now it follows the latest response to either the main conversation or a subagent, which is a helper Claude runs separately for a task. It clears when the limiter reports no grace use. It ignores:

  • side calls outside the main conversation and subagents
  • responses that carry no usage-limit status
  • refusals of requests that were over the limit
Why

The grace indicator may now turn on and off at different moments than before. The request for extended usage is sent only when a server-side switch allows it, and that switch is off unless it is turned on remotely.

Read from
Feature flag
tengu_lantern_spool Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.282: 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.282. 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 off for tengu_lantern_spool, 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 on for tengu_lantern_spool, 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 off for tengu_lantern_spool, 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 on for tengu_lantern_spool, 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 off for tengu_lantern_spool, 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 on for tengu_lantern_spool, 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 off for tengu_lantern_spool, 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 on for tengu_lantern_spool, 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 doubtOnly the description of the signal changed visibly, so it is not confirmed that the code computing it changed the same way.

See this entry in the whole of v2.1.282 →

Feedback