{"version":"2.1.288","anchor":"usage-limit-wait-gate-and-tengu-twinkling-swan-clamp-added","canonical_anchor":"usage-limit-wait-gate-and-tengu-twinkling-swan-clamp-added","heading":"Groundwork for how long workflows pause at a usage limit","tier":"soon","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/usage-limit-wait-gate-and-tengu-twinkling-swan-clamp-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Groundwork for how long workflows pause at a usage limit\n\nWorkflow pauses for usage limits gain a check on whether they would wait, plus a new remotely set number with a cap\n\n**Unclear.** It is not clear what the new number controls or what uses the new check.\n\n**What**\n\nWhen 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.\n\nClaude 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.\n\n**Why**\n\nThis could change how long agents pause while waiting for a usage limit to reset.\n\n- Flag `tengu_twinkling_swan`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Usage & Limits\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}