{"version":"2.1.318","anchor":"stale-lock-sweep-skips-unreadable-lock-files","canonical_anchor":"stale-lock-sweep-skips-unreadable-lock-files","heading":"Stale lock cleanup now keeps lock files it cannot read","tier":"notice","area":"Auto-Updater","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/stale-lock-sweep-skips-unreadable-lock-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Stale lock cleanup now keeps lock files it cannot read\n\nBefore deleting an old lock file, Claude Code now reads it, and keeps any it cannot read\n\n**What**\n\nLock files are small markers Claude Code uses to show something is in use. When Claude Code clears out old ones, it now reads each file first and also looks at what is in it when deciding whether the lock is stale. If a lock cannot be read, Claude Code keeps it and logs \"Skipping stale-lock sweep of unreadable lock\". Before, a lock was deleted as soon as the check on its owner failed.\n\n**Why**\n\nThis avoids deleting locks that are still held by a running copy of Claude Code.\n\n- Area: Auto-Updater\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}