Messages between your sessions verify the process on the other end before writing.
What's wrong with this entry?
When 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.
- The process-ID check only applies when the caller supplies an expected ID; it is skipped on Windows.
- Startup socket bind time is now recorded, along with whether the bind succeeded.
Refusing to send: connected endpoint is not the expected process
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.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross