{"version":"2.1.248","anchor":"stricter-checks-before-connecting-to-a-peer-session","canonical_anchor":"stricter-checks-before-connecting-to-a-peer-session","heading":"Stricter checks before connecting to a peer session","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/stricter-checks-before-connecting-to-a-peer-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Stricter checks before connecting to a peer session\n\nConnecting to another session's socket now verifies the process id and owner first.\n\n**What**\n\nBefore connecting to another session's socket, Claude now verifies the peer's process id and that the socket is owned by an expected user id, rather than trusting the path alone.\n\n**Details**\n\n- Messaging state gained fields for the accepted owner user ids, an in-flight start marker, and the last start-failure detail.\n\n**Evidence**\n\n`peerDirOwnerUids`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}