{"version":"2.1.236","anchor":"cross-session-messages-check-who-they-are-writing-to","canonical_anchor":"cross-session-messages-check-who-they-are-writing-to","heading":"Cross-session messages check who they are writing to","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/cross-session-messages-check-who-they-are-writing-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Cross-session messages check who they are writing to\n\nMessages between your sessions verify the process on the other end before writing.\n\n**What**\n\nWhen one Claude Code session sends to another over a local socket, it now refuses to follow a symlinked reply target, and on macOS and Linux can compare the process ID on the other end of the connection against the one it expected, aborting the write on a mismatch or an unreadable ID.\n\n**Details**\n\n- The process-ID check only applies when the caller supplies an expected ID; it is skipped on Windows.\n- Startup socket bind time is now recorded, along with whether the bind succeeded.\n\n**Evidence**\n\n`Refusing to send: connected endpoint is not the expected process`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}