What
Claude 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.
Details
- The handshake advertises a third capability string,
reply_across_default_dirs, alongside the existing notify-idle and artifact-yield ones. - Accepted directories are matched by fixed patterns for
/tmp/cc-socks,/private/tmp/cc-socks,/run/user/<uid>/cc-socksand the Termux tmp path, and the uid component must match the listener's own uid list. - The receiving side accepts cross-directory replies when the peer process id was verified through peer credentials.
- No remote config flag: it is advertised whenever the platform is not Windows and the runtime exposes
Bun.ant.getPeerPid.
Evidence
reply_across_default_dirs
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/run
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /run, on Claude Science changelog.
* Claude Science is now available for Windows: download it from [claude.com/product/claude-science](https://claude.com/product/claude-science), and see [Run on Windows](/docs/claude-science/run-on-windows) for requirements and setupclaude-science/changelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /run, on Claude Science changelog.
Anthropic's release notes agree
Improved cross-session messaging: falls back to a private per-user /tmp directory when the default one can't be used, and the notice and…