{"version":"2.1.296","anchor":"path-validator-now-rejects-backslashes","canonical_anchor":"path-validator-now-rejects-backslashes","heading":"Paths containing a backslash are now refused by a safety check","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/path-validator-now-rejects-backslashes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Paths containing a backslash are now refused by a safety check\n\nA path safety check in Claude Code now rejects any path containing a backslash\n\n**Unclear.** Which feature uses this check, and so where a path with a backslash will now be refused, is not known.\n\n**What**\n\nClaude Code checks some file paths before using them. That check already refused paths that start with `-` or `:`, or that contain `=>`. It now also refuses any path that contains a backslash (`\\`).\n\n**Why**\n\nThis is a safety measure. Windows-style paths, which use backslashes, and paths with escaped characters used to pass this check and are now turned away.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}