Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
In DevelopmentKind: in v2.1.288,
In DevelopmentSection of the release
What
When you hit a usage limit, automated workflows can pause until the limit resets. The part that handles this gains a check that answers whether it would wait for a given reset time, based on the conditions it already uses.
Claude Code also gains a new number read from its remote settings. It accepts a number or a number written as text, and keeps it between zero and a fixed maximum. When the server sends nothing, a built-in value is used.
Why
This could change how long agents pause while waiting for a usage limit to reset.
Read from
Feature flag
tengu_twinkling_swanNot 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.288: 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.
Flag reading movedThe flag server now returns 60000 for tengu_twinkling_swan, 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 movedThe flag server now returns nothing at all, having stopped carrying it for tengu_twinkling_swan, 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.
