{"version":"2.1.283","anchor":"worktree-creation-containment-check-now-tolerates-case-foldi","canonical_anchor":"worktree-creation-containment-check-now-tolerates-case-foldi","heading":"Creating a worktree no longer fails over upper and lower case differences in paths","tier":"notice","area":"Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/worktree-creation-containment-check-now-tolerates-case-foldi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Creating a worktree no longer fails over upper and lower case differences in paths\n\nClaude Code's worktree location check now tolerates case differences on case-insensitive systems, avoiding false \"Cannot create worktree\" errors\n\n**Unclear.** Exactly what the on-disk confirmation checks is not settled.\n\n**What**\n\nA git worktree is a second working copy of a repository kept in a separate folder. When Claude Code creates one, it checks that the folder it ended up with is the one it expected.\n\nThat check used to be a strict text comparison of the two paths. It now works in steps:\n\n- It first compares the two paths after tidying them up, as before.\n\n- On systems where file names ignore upper and lower case, it then compares case-insensitive versions of the paths.\n\n- It confirms that match against the files on disk.\n\n**Why**\n\nOn macOS or Windows, a path that differed only in letter case could make Claude Code refuse to create the worktree with a \"Cannot create worktree\" error, even though both paths pointed to the same folder.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}