Claude Code starts even if something odd is sitting at its lock file path.
What's wrong with this entry?
If a directory, fifo, socket or symlink sits at the daemon lock path, Claude Code now removes it and retries once instead of failing to start.
EISDIRandENXIOerrors during removal trigger the same cleanup; a symlink loop (ELOOP) is treated as an existing lock and left alone.- The warning is logged once per process.
removing it as the legacy path does
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.223
Daemon lock can now live in the v5 storage backend
Both mention daemon
-
v2.1.246
Background daemon start failures are classified, and a sleeping machine gets one retry
Both mention daemon
-
v2.1.248
Background daemon can retire a same-version instance
Both mention daemon