{"version":"2.1.295","anchor":"remote-stream-reconnect-regained-telemetry-and-stale-stream","canonical_anchor":"remote-stream-reconnect-regained-telemetry-and-stale-stream","heading":"Remote session connections handle reconnects more carefully","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/remote-stream-reconnect-regained-telemetry-and-stale-stream","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Remote session connections handle reconnects more carefully\n\nWhen a remote session's connection comes back, Claude Code records the outage and ignores data from a stream it has replaced\n\n**What**\n\nA remote session streams its output to Claude Code over a live connection. When that connection drops and comes back, Claude Code now records how long it was down and how many attempts it took to reconnect. The length of the outage is now measured from the moment the connection went down, rather than from the last moment it was known to be healthy.\n\nWhen Claude Code replaces a connection with a new one, it now stops reading from the old one.\n\n**Why**\n\nIgnoring the old connection stops leftover data from a replaced stream being handled as if it were current. The new record gives a clearer picture of how often and for how long remote sessions lose their connection.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}