Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

One retry after a usage-limit rejection, controlled by a remote switch

Claude Code has code to resend a request once after it is rejected for hitting a five-hour or seven-day usage limit, behind a remote switch

You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

Unclear It is not stated how the remote switch controls the retry, so whether the retry happens for anyone is unclear.

What

Claude Code now contains code that resends a request one time after the server turns it down because a usage limit was reached. It applies only when the rejection names the five-hour or the seven-day limit. The behaviour is tied to a switch that the server can set, which falls back to false when the server sends nothing.

Why

This points towards a short grace period, where a request that just crossed a usage limit gets one more attempt instead of failing straight away.

Read from
Feature flag
tengu_glittery_tower_killswitch 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.318: 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.318. It isn't a statement about your account. What a flag value here can and cannot tell you

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 stated how the remote switch controls the retry, so whether the retry happens for anyone is unclear.
The name it cites is new in this buildNew in this build: tengu_glittery_tower_killswitch

See this entry in the whole of v2.1.318 →

Feedback