{"version":"2.1.323","anchor":"editwrite-now-refuse-protected-paths-with-a-second-permissi","canonical_anchor":"editwrite-now-refuse-protected-paths-with-a-second-permissi","heading":"File edits and writes now go through extra permission checks","tier":"notice","area":"File Tools","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/editwrite-now-refuse-protected-paths-with-a-second-permissi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### File edits and writes now go through extra permission checks\n\nClaude Code's file edit and write tools now run two more checks on the target path before writing, so some writes that used to pass may be refused\n\n**Unclear.** It is not clear exactly which paths the new checks refuse.\n\n**What**\n\nThe tools Claude uses to edit and create files now check the target path more strictly before writing. Before, they ran one permission check. Now they also test your permission rules against the path the file actually resolves to, and run a further check on the path. One of the refusals concerns writes into the memory directory where the path only turns out to be refused after escaped characters in it are decoded.\n\n**Why**\n\nWriting files is sensitive, so stricter checks make it harder for a write to land somewhere it should not. The flip side is that some edits or writes that were allowed before may now be refused, for example where the path goes through a symbolic link (a shortcut to another location).\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}