Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Cross-session peers accept reply sockets in the standard socket directories

Under the hood
Useful1 Signal2
Cross-Session Messaging not in their notes

Sessions accept reply sockets in any standard socket directory, not just their own.

/run
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-socks and 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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →