{"version":"2.1.232","anchor":"peer-session-lookup-says-when-the-local-machine-could-not-be","canonical_anchor":"peer-session-lookup-says-when-the-local-machine-could-not-be","heading":"Peer session lookup says when the local machine could not be listed","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/peer-session-lookup-says-when-the-local-machine-could-not-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Peer session lookup says when the local machine could not be listed\n\nIf Claude can't list local sessions when routing a message, it says so instead of claiming no match.\n\n**What**\n\nWhen Claude Code cannot enumerate the sessions running on this machine while resolving which session to message, it now says so instead of implying no match exists.\n\n**Details**\n\n- New messages: \"the sessions on this machine could not be listed just now\" and \"this machine's and your account's other sessions could not all be checked just now\".\n- The condition also blocks the shortcut that auto-picks a single obvious match, so you are asked rather than silently routed.\n- The same state is included in the diagnostic payload for the lookup.\n\n**Evidence**\n\n`the sessions on this machine could not be listed just now`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}