{"version":"2.1.312","anchor":"session-lock-check-skips-when-not-interactive","canonical_anchor":"session-lock-check-skips-when-not-interactive","heading":"Session lock check no longer starts a duplicate check in some cases","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/session-lock-check-skips-when-not-interactive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Session lock check no longer starts a duplicate check in some cases\n\nWhen a session lock is already held or being checked and a certain condition is false, Claude Code now stops early instead of starting another check\n\n**Unclear.** It is not clear what this lock protects or which condition decides whether the check is skipped.\n\n**What**\n\nClaude Code uses a lock to manage the session host. It now handles one case differently. When the lock is already held, or a check on it is already in progress, and a certain condition is false, Claude Code stops early and does not start a new check.\n\nBefore this release, it always scheduled a check whenever nothing was held, with no early exit.\n\n**Why**\n\nThis changes how Claude Code manages the session host over its lifetime, because a second check is no longer started when one is already under way.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}