{"version":"2.1.248","anchor":"local-ipc-sends-verify-the-peer-s-owner-and-process-identity","canonical_anchor":"local-ipc-sends-verify-the-peer-s-owner-and-process-identity","heading":"Local IPC sends verify the peer's owner and process identity","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/local-ipc-sends-verify-the-peer-s-owner-and-process-identity","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Local IPC sends verify the peer's owner and process identity\n\nMessages to other local Claude Code processes now verify socket ownership and process identity.\n\n**What**\n\nWhen Claude Code sends a message to another local Claude Code process over its messaging socket and expects a specific process id, it now also checks that the socket endpoint is owned by your uid and that the peer's process start token matches, so a recycled pid or another user's socket is refused.\n\n**Details**\n\n- Refusal message: \"Refusing to send: connected endpoint is a different process with the expected pid\".\n- Callers pass a new `expectPeerProcStart` option; the session-rename notice path supplies both pid and start token.\n- No flag; applies whenever a peer pid is expected, and not on Windows.\n\n**Evidence**\n\n`Refusing to send: connected endpoint is a different process with the expected pid`\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}