{"version":"2.1.227","anchor":"daemon-lock-recovers-when-the-lock-path-is-not-a-regular-fil","canonical_anchor":"daemon-lock-recovers-when-the-lock-path-is-not-a-regular-fil","heading":"Daemon lock recovers when the lock path is not a regular file","tier":"notice","area":"Daemon","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/daemon-lock-recovers-when-the-lock-path-is-not-a-regular-fil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Daemon lock recovers when the lock path is not a regular file\n\nClaude Code starts even if something odd is sitting at its lock file path.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- `EISDIR` and `ENXIO` errors during removal trigger the same cleanup; a symlink loop (`ELOOP`) is treated as an existing lock and left alone.\n- The warning is logged once per process.\n\n**Evidence**\n\n`removing it as the legacy path does`\n\n- Area: Daemon\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}