{"version":"2.1.286","anchor":"lock-owner-check-missing-owner-record-distinguishes-lock-ch","canonical_anchor":"lock-owner-check-missing-owner-record-distinguishes-lock-ch","heading":"Lock checks now tell a changed lock apart from one with no owner","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/lock-owner-check-missing-owner-record-distinguishes-lock-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Lock checks now tell a changed lock apart from one with no owner\n\nWhen a lock has no owner record, Claude Code now checks whether the lock file changed and reports that case separately\n\n**Unclear.** Which lock this check applies to is not stated.\n\n**What**\n\nClaude Code uses a lock file so that two processes do not act on the same thing at once. When it checks a lock and finds no record of who owns it, it now looks at the lock file again:\n\n- if the file's last-modified time is the one expected, it reports that there is no owner record, as before\n\n- if the time is different, it reports that the lock changed\n\nIt used to report that there was no owner record in both cases.\n\n**Why**\n\nThis makes the diagnosis a little more precise. A lock that was replaced in the meantime is no longer mistaken for one that simply has no owner.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}