Startup survives when another Claude Code already holds the socket path, retrying nearby.
What's wrong with this entry?
When Claude Code picks its own local socket path for inter-process messaging, it now probes the existing file first: a leftover from a dead process is deleted and retried, and a socket a live sibling is using causes a bind at a randomised nearby path, up to three attempts. Sockets moved aside on earlier runs are cleaned up. A socket path you specify explicitly still fails hard if it is in use.
- The failure message after three attempts warns that siblings may be in a different pid namespace, which is why liveness could not be judged.
listen EADDRINUSE on the auto socket path and its moved-aside siblings
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
Startup prefetch failures no longer surface
Both mention startup
-
v2.1.239
Deleted working directories are detected at startup and handled during hooks
Both mention startup
-
v2.1.246
Startup banner summarising what changed since you last read the release notes
Both mention startup