Messages to other local Claude Code processes now verify socket ownership and process identity.
What's wrong with this entry?
When 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.
- Refusal message: "Refusing to send: connected endpoint is a different process with the expected pid".
- Callers pass a new
expectPeerProcStartoption; the session-rename notice path supplies both pid and start token. - No flag; applies whenever a peer pid is expected, and not on Windows.
Refusing to send: connected endpoint is a different process with the expected pid
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