Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.229 ·

Rate-limit banner can queue an automatic continue at reset

Hitting a five-hour limit could queue your turn to resume automatically at reset, currently off.

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

Auto-continue-after-reset and a prefilled 'continue' prompt are built but sit behind a flag that falls back to off.

What

When you hit a five-hour limit and the reset time is known, Claude Code can queue your turn to resume after the reset and show a hint line ending in " to continue after reset", or prefill continue into the prompt. Choosing "adjust" or "upgrade" from the rate-limit or spend-limit menu cancels the queued continue; cancelling or choosing "wait" prefills it instead. The whole path is behind the tengu_vellum_anchor flag, which falls back to off, so nothing in this build turns it on locally and whether it appears is decided by server config.

Details
Evidence

tengu_rl_checkpoint_auto_continue_queued, Press

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_vellum_anchor 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.229: 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.229. 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_vellum_anchor, 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 nothing at all, having stopped carrying it for tengu_vellum_anchor, 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
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_vellum_anchor

See this entry in the whole of v2.1.229 →

Feedback