{"version":"2.1.312","anchor":"remote-peer-unreachable-message-adds-a-leftfor-variant","canonical_anchor":"remote-peer-unreachable-message-adds-a-leftfor-variant","heading":"Remote sessions and hosts can record that they left, and why","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-peer-unreachable-message-adds-a-leftfor-variant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions and hosts can record that they left, and why\n\nRemote sessions, remote-tool hosts and unreachable-peer messages now carry a 'left' state with a leftFor reason instead of a fixed off reason\n\n**What**\n\nWith Remote Control, one Claude Code session can reach another session or a remote host (a peer). Claude Code can now record that a peer or session left on purpose, and why.\n\n- Closing a remote session through `dispose` can now take a `leftFor` value. When it is set, the session records `at: \"left\"` and passes `leftFor` on to the close step.\n\n- The registry of remote-tools hosts now tracks each host's capabilities and which instance announced it. It also records why a host was withdrawn, through `withdrawnFor`.\n\n- The session report has a new `left` state. It shows as `state: \"off\"` with a reason taken from `leftFor`. Before, the reason could only be `serving_off` or `not_announced`.\n\n- When a peer that signed off has `leftFor` set, the message saying it \"could not be reached from this session\" is now built from that value. Before, it always asked the user to open Claude on that machine again with Remote Control on.\n\nThe same finding also notes two other changes. Cloud-session `status` and `stopping` events now show no notice text. Permission asks in a cloud session now pass `forMcpSkill` when the tool's metadata has `mcpSkill`.\n\n**Why**\n\nA peer or host that left on purpose is no longer reported as simply off or unannounced. Claude, and anyone reading the session report, gets the actual reason, so a deliberate departure no longer leads to the generic advice to turn Remote Control back on.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}