You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.250,
What probably matters to youSection of the release
A lease-aware short-retry tier exists but lease mode (tengu_slate_lantern_ember) falls back to off, so stock builds never use it.
What
The reconnect delay picker now has two tiers. The long one, 120 to 240 seconds, is used on the second and later attempts of a stall run when the close was Cloudflare-mitigated, lease mode is off, there is no lease, or the lease will not outlive the next attempt. Lease mode is tengu_slate_lantern_ember with fallback false, so without a remote value every repeat stall takes the long tier.
Details
Short tier remains 30 to 60 seconds.
The timing table is a plain in-bundle constant, never reassigned, so the numbers are not server-tunable.
Evidence
longStallMaxMs: 240000,
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_slate_lantern_emberOff by default, switched on for this account
The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.250: off
Flag reading movedThe flag server now returns on for tengu_slate_lantern_ember, 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_slate_lantern_ember, 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.
