{"version":"2.1.304","anchor":"realpath-rejects-paths-containing-backslashes","canonical_anchor":"realpath-rejects-paths-containing-backslashes","heading":"Paths with backslashes are no longer resolved as separators","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/realpath-rejects-paths-containing-backslashes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Paths with backslashes are no longer resolved as separators\n\nClaude Code now declines to resolve a path when a backslash in it would be read as a folder separator\n\n**What**\n\nWhen Claude Code works out the real location of a file, it now checks first whether a backslash in the path would be read as a folder separator. If so, it stops and leaves the path unresolved, with the code `EBACKSLASH`, instead of trying to resolve it.\n\n**Why**\n\nOn macOS and Linux, a backslash is an ordinary character in a file name, so treating it as a separator could point to the wrong file. Such paths are now left alone rather than resolved incorrectly.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}