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

Claude Code v2.1.247 ·

Endless stream reconnection is built but off in this build

The cloud event stream could redial forever, but nothing turns that on so it still gives up.

Nothing to try yet In Development
JSON All of v2.1.247
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.247,
In DevelopmentSection of the release

Endless reconnection is implemented but no caller enables it; the 5-attempt budget still applies.

What

The cloud session's event-stream client can be told to keep redialling forever instead of giving up after 5 reconnect attempts. Nothing in this build turns it on, so behaviour is unchanged: the budget runs out and the stream closes.

Details
  • When on, exhausting the budget keeps retrying at the maximum backoff delay indefinitely, logs the attempt count as ∞, stops firing the reconnecting callback, and sends a one-shot telemetry event the first time it passes the budget.
  • The mode reads from two places: a keepStreamRedialling config key, which nothing in the build ever writes, and an instance flag set only by a method that has no caller anywhere in the bundle.
  • The intent is a machine that is serving device hooks or remote tool calls for a cloud session and must stay dialled in.
Evidence

remote_connect_redialling_past_budget

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

See this entry in the whole of v2.1.247 →

Feedback