{"version":"2.1.287","anchor":"windows-msys-paths-normalized-in-write-permission-checks","canonical_anchor":"windows-msys-paths-normalized-in-write-permission-checks","heading":"Protected-folder checks on Windows now understand Git Bash style paths","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/windows-msys-paths-normalized-in-write-permission-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Protected-folder checks on Windows now understand Git Bash style paths\n\nOn Windows, paths like \/c\/... or \/cygdrive\/c\/... are converted to normal Windows paths before Claude Code checks whether a write is allowed\n\n**What**\n\nBefore Claude Code writes to a file, it checks whether the path points into a protected location. On Windows, it now also converts paths written in the Git Bash or Cygwin style, such as `\/c\/Users\/...` or `\/cygdrive\/c\/Users\/...`, into ordinary Windows paths like `C:\\Users\\...`, and checks the converted path against the protected locations too. Before, only the path exactly as written was checked. This applies only on Windows.\n\n**Why**\n\nThis closes a gap where writing a path in Git Bash style could get past the check that protects certain locations from being written to.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}