{"version":"2.1.287","anchor":"cwd-registration-check-now-compares-paths-with-alias-and-unc","canonical_anchor":"cwd-registration-check-now-compares-paths-with-alias-and-unc","heading":"Registering your working folder as a cloned repo is caught across path forms","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cwd-registration-check-now-compares-paths-with-alias-and-unc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Registering your working folder as a cloned repo is caught across path forms\n\nClaude Code now spots the session's working folder even when it is written with different case, an alias, or a Windows network path\n\n**What**\n\nClaude Code refuses to register the session's working directory (the folder it was started in) as a cloned repository, because that folder is already registered. The check used to compare the two paths as exact text. It now treats paths as the same folder even when they differ in:\n\n- Letter case\n\n- Alias forms of the same folder\n\n- Windows network path (UNC) form, such as `\\\\server\\share`\n\nThe error message now refers to \"the session's working directory\" and tells you to pass the cloned repository's own directory instead.\n\n**Why**\n\nPaths that point to the same folder through a link or a network path are no longer missed by this check.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}