{"version":"2.1.307","anchor":"worker-heartbeat-late-socket-answers-handled-and-socket-ren","canonical_anchor":"worker-heartbeat-late-socket-answers-handled-and-socket-ren","heading":"Remote sessions handle slow heartbeats and sign-in renewals better","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/worker-heartbeat-late-socket-answers-handled-and-socket-ren","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Remote sessions handle slow heartbeats and sign-in renewals better\n\nA late heartbeat reply on the worker connection now counts as success, and a refreshed sign-in token now renews that connection\n\n**What**\n\nWhen Claude Code runs as a worker for a remote session, it sends a regular heartbeat, a short message that says the session is still alive. It sends this over a live connection to the server, called the worker socket, and falls back to an ordinary web request if that fails. Two things are different now:\n\n- A heartbeat that is answered late on the socket now counts as a success, even if the fallback web request failed, so it is not counted as a missed heartbeat.\n\n- When Claude Code's sign-in token is refreshed, the socket connection is now renewed with the new token.\n\nBefore, the heartbeat used a single request, and a refreshed token renewed a different connection.\n\n**Why**\n\nRemote sessions should drop less often on unreliable network connections.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}