{"version":"2.1.302","anchor":"git-worktree-gitdir-check-rejects-backslash-paths-on-posix","canonical_anchor":"git-worktree-gitdir-check-rejects-backslash-paths-on-posix","heading":"Git worktree lookups ignore paths containing backslashes on macOS and Linux","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/git-worktree-gitdir-check-rejects-backslash-paths-on-posix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Git worktree lookups ignore paths containing backslashes on macOS and Linux\n\nOn non-Windows systems, Claude Code no longer follows a worktree's git directory pointer when any path involved contains a backslash\n\n**What**\n\nA git worktree is an extra working copy of a repository that shares the same history. It keeps a small `.git` file that points to where its git data really lives. When Claude Code resolves that pointer on macOS, Linux or any other non-Windows system, it now checks the paths involved. If any of them contains a backslash, Claude Code does not follow the pointer and keeps the original path instead.\n\n**Why**\n\nThis is a security hardening. A crafted `.git` file can no longer use backslash paths to steer Claude Code to an unexpected location.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}