Messaging socket setup now creates and locks down its directory and explains custom-path failures.
What's wrong with this entry?
Before binding the socket used for messaging between sessions, Claude Code now creates the parent directory and sets it to owner-only (0700), then removes any stale socket. If you passed --messaging-socket-path yourself and it fails, the error tells you what to do.
- The message is "Choose a different --messaging-socket-path whose directory you own and can make private (0700)."
- A path not given explicitly is resolved to an absolute path first.
Choose a different --messaging-socket-path whose directory you own and can make private (0700).
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.247
--messaging-socket-pathnow errors instead of silently doing nothingBoth mention socket path
-
v2.1.224
Session info reports the messaging socket path
Both mention socket path
-
v2.1.224
Local messaging socket: where it lives, who can read it, and refusing to steal a live one
Both mention socket path