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

Replayed history no longer makes a dead cloud worker look alive

After reconnecting, replayed old output no longer makes a dead cloud worker look alive.

You'll notice Bug Fixes
JSON All of v2.1.247
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
Bug FixesKind: in v2.1.247,
Bug FixesSection of the release
What

After reconnecting and resuming from a saved position, the CLI could treat old frames being replayed as evidence that the remote worker was still running. Frames are now compared against the time the current connection opened and marked as replayed if they predate it, and only fresh worker frames count as proof of life.

Details
  • The comparison allows 2 seconds of slack; a frame whose date cannot be parsed is conservatively treated as replayed.
  • The connection time comes from the response date header when the server sends one.
  • Frames also carry a worker epoch integer read off the frame.
  • Applies to all cloud sessions on this build, with no setting to turn it off.
Evidence

t.source === "worker" && t.replayed !== !0, connectedSince

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