{"version":"2.1.248","anchor":"cross-session-peers-accept-reply-sockets-in-the-standard-soc","canonical_anchor":"cross-session-peers-accept-reply-sockets-in-the-standard-soc","heading":"Cross-session peers accept reply sockets in the standard socket directories","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cross-session-peers-accept-reply-sockets-in-the-standard-soc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cross-session peers accept reply sockets in the standard socket directories\n\nSessions accept reply sockets in any standard socket directory, not just their own.\n\n**What**\n\nClaude Code sessions on one machine talk over local sockets. A session now tells its peers it can handle a reply socket living in any of the standard socket directories, not only the exact directory its own socket sits in. On by default on macOS and Linux; never on Windows.\n\n**Details**\n\n- The handshake advertises a third capability string, `reply_across_default_dirs`, alongside the existing notify-idle and artifact-yield ones.\n- Accepted directories are matched by fixed patterns for `\/tmp\/cc-socks`, `\/private\/tmp\/cc-socks`, `\/run\/user\/<uid>\/cc-socks` and the Termux tmp path, and the uid component must match the listener's own uid list.\n- The receiving side accepts cross-directory replies when the peer process id was verified through peer credentials.\n- No remote config flag: it is advertised whenever the platform is not Windows and the runtime exposes `Bun.ant.getPeerPid`.\n\n**Evidence**\n\n`reply_across_default_dirs`\n\n- Area: Cross-Session Messaging\n- Names: `\/run`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}