{"version":"2.1.295","anchor":"remote-session-list-shows-went-to-sleep-for-asleep-session","canonical_anchor":"remote-session-list-shows-went-to-sleep-for-asleep-session","heading":"Offline remote sessions can now be reported as asleep","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/remote-session-list-shows-went-to-sleep-for-asleep-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Offline remote sessions can now be reported as asleep\n\nWhen another session is offline, the model is now told if it went to sleep instead of always being told it failed a liveness check\n\n**What**\n\nClaude Code keeps a list of other sessions it can reach. A session is one running conversation with Claude Code. When one of them is offline, the status line about it used to always say it did not answer a liveness check, which is an automatic test of whether it is still running. That line can now say instead that the session went to sleep.\n\n**Why**\n\nThe model gets a more accurate reason for a session being offline, so it can treat a sleeping session differently from one that has stopped responding.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}