{"version":"2.1.312","anchor":"bridge-unicode-path-validation-changed","canonical_anchor":"bridge-unicode-path-validation-changed","heading":"Paths with Unicode spaces in the middle are now accepted","tier":"notice","area":"File Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/bridge-unicode-path-validation-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Paths with Unicode spaces in the middle are now accepted\n\nA path safety check now allows unusual Unicode spaces inside a path but still rejects them at the end of a path segment\n\n**What**\n\nClaude Code checks file paths to make sure they are safe. A segment is one part of a path between slashes. This check now treats Unicode space characters differently. Unicode space characters are spacing characters other than the ordinary space.\n\n- Spaces inside a segment: an unusual Unicode space no longer causes the whole path to be rejected.\n\n- Spaces at the end of a segment: a segment that ends in a Unicode space other than the ordinary space is still rejected.\n\n- Dots and spaces only: a segment made up only of dots and spaces, including Unicode spaces, is still rejected.\n\n- Two characters, U+2000 and U+2001, are now always refused.\n\n**Why**\n\nSome paths that were refused before, because they contained an unusual space character in the middle, are now allowed. Trailing spaces, which are easy to miss when you read a path, are still blocked.\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}