{"version":"2.1.191","anchor":"worktree-lock-check-improvement","canonical_anchor":"worktree-lock-check-improvement","heading":"Worktree Lock Check Improvement","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191\/e\/worktree-lock-check-improvement","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191","markdown":"### Worktree Lock Check Improvement\n\nWhat changed: The worktree entry check now parses the git lock reason string rather than calling a generic lock-owner function, so it correctly identifies lock entries written by Claude Code agents specifically. A locked worktree from a different tool no longer prevents entry.\n\n**Details**\n\n- Pattern matched: `claude agent <name> (pid <N>[ start <time>])`\n- Only if the matching PID is running and confirmed to be a Claude Code process is the `Cannot enter worktree` error raised.\n\n**Evidence**\n\nWorktree lock parsing (search for `\"claude agent .+ \\\\(pid\"`)"}