{"version":"2.1.299","anchor":"project-context-loading-distinguishes-lock-contention-and-re","canonical_anchor":"project-context-loading-distinguishes-lock-contention-and-re","heading":"Project context skipped because of a lock can be read again","tier":"internal","area":"Context Management","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/project-context-loading-distinguishes-lock-contention-and-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Project context skipped because of a lock can be read again\n\nWhen Claude Code skips loading project context because another process holds a lock, it now marks that context as worth reading again\n\n**What**\n\nWhen Claude Code skips loading a project's context, it now says why. If the reason is that another process was holding a lock on it at the time, the result is marked as worth reading again. Previously a skip gave no reason at all.\n\n**Why**\n\nContext missed only because of a brief clash with another process can now be picked up on a later try.\n\n- Area: Context Management\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}