{"version":"2.1.314","anchor":"auto-mode-write-check-gains-a-not-as-judged-outcome","canonical_anchor":"auto-mode-write-check-gains-a-not-as-judged-outcome","heading":"Auto mode write check can refuse paths that were not reviewed","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/auto-mode-write-check-gains-a-not-as-judged-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Auto mode write check can refuse paths that were not reviewed\n\nIn auto mode, a write is no longer treated as safe if its real path is not on the list of paths that were reviewed\n\n**Unclear.** It is not clear whether the list of reviewed paths is ever passed in, so the new check may not run yet.\n\n**What**\n\nAuto mode lets Claude Code decide some permission questions itself instead of asking you each time. Part of it checks whether writing to a file path is safe enough to allow without asking. That check can now be given a list of paths that were already reviewed. If the actual path, after resolving it, is not on that list, the check gives a new answer meaning the path does not match what was reviewed.\n\nThis new check runs after the existing ones for paths outside your home folder and for writes that would normally ask you first.\n\n**Why**\n\nIt makes it harder for a write to be treated as safe when the file it really touches is not the one that was reviewed.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}