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.250 ·

Failed live-watch startups are treated as temporary outages and retried on the slow schedule

Live artifact watches that fail to start from a server hiccup now retry on the patient schedule instead of burning attempts.

You'll notice In Development
JSON All of v2.1.250
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.250,
In DevelopmentSection of the release
What

When a live artifact watch fails to start, Claude Code now decides whether the failure looks like a transient server problem rather than a permanent one, and routes it to the slow stall-style retry instead of the fast consecutive-failure backoff. A failure counts as a temporary outage if the server replied with a retryable status, or if the request produced no reply at all and hung for at least 10 seconds. Neither of these markers existed on this error path in 2.1.248.

Details
  • The retryable-status test returns true for HTTP status 500 or above, 429 and 408; such a status attaches an unavailable marker to the startup response.
  • A startup error code of boot_request_error attaches a noAnswer marker, meaning the request errored out with no reply.
  • The startup builder records the time just before the request is issued, so a hung startup can be measured; a noAnswer result plus elapsed time of at least stallThresholdMs, the reconnect timing default compiled at 10000 ms, counts as unavailable.
  • The failure helper gained unavailable and httpStatus options and passes a stalled flag plus the HTTP status into the reconnect scheduler.
  • All of this sits inside the live-watch feature, which is off unless the tengu_slate_lantern flag is switched on for your account.
Evidence

boot_request_error, ...(i.errorCode === "boot_request_error" && { noAnswer: !0 }),

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

Read from
Feature flag
tengu_slate_lantern Off 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

Read once, for one account on one subscription tier, against v2.1.250. 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 on for tengu_slate_lantern, 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 off for tengu_slate_lantern, 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 on for tengu_slate_lantern, 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_slate_lantern, 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 →

See this entry in the whole of v2.1.250 →

Feedback