{"version":"2.1.293","anchor":"remote-liveness-timer-records-last-healthy-time","canonical_anchor":"remote-liveness-timer-records-last-healthy-time","heading":"Remote session connection checks record the last healthy moment and use a new timeout","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remote-liveness-timer-records-last-healthy-time","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remote session connection checks record the last healthy moment and use a new timeout\n\nThe connection check for remote sessions now records when the connection was last healthy and uses a different timeout value\n\n**Unclear.** Whether the new timeout for remote sessions is longer or shorter than before is not known.\n\n**What**\n\nFor remote sessions, Claude Code keeps a timer that notices when the connection has gone quiet for too long. A session is one conversation with Claude Code. Each time this timer restarts, Claude Code now records the moment the connection was last known to be healthy. The timer also now uses a different timeout value from before.\n\n**Why**\n\nThe change to the timeout may change how long a remote session can go quiet before Claude Code treats the connection as lost.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}