Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.227 Home All releases olderv2.1.226 v2.1.228newer
Claude Code v2.1.227

Daemon lock recovers when the lock path is not a regular file

You'll notice
Useful2 Signal1
Daemon

Claude Code starts even if something odd is sitting at its lock file path.

What

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.

Details
  • EISDIR and ENXIO errors 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.
Evidence

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.

See this entry in the whole of v2.1.227 →