Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Remote stream connection tracks machine sleep and clears its new timers on close

The remote session stream adds a monotonic liveness clock, a sleep listener and a frame-wait timer, and clears them all when the connection closes

Group of 2 You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

Unclear It is not settled whether time spent asleep is now actually excluded from the disconnect check.

What

Remote and hosted sessions keep a live stream open to Claude Code and check that it is still alive. That stream is called an SSE connection, a long-lived link that the server sends updates down. The part that handles this connection gains new pieces.

  • lastLivenessEvidenceMonotonicMs records the last sign of life on a monotonic clock, a timer that only moves forward and is not affected by changes to the system clock. Before, only a wall-clock time (lastLivenessEvidenceAtMs) was kept.
  • stopListeningForSleep belongs to a new listener for the computer going to sleep.
  • frameWaitTimer is a new timer.
  • Closing the connection now stops the sleep listener and clears frameWaitTimer, as well as the reconnect and liveness timers it already cleared.

Why

These pieces suggest that time a laptop spends asleep may no longer be counted as the connection going silent. That could stop false disconnects after waking the machine. Clearing the new timers on close stops them firing, or triggering a stray reconnect, after the connection has ended.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not settled whether time spent asleep is now actually excluded from the disconnect check.

See this entry in the whole of v2.1.318 →

Feedback