{"version":"2.1.319","anchor":"auto-mode-rule-attribution-and-untrusted-folder-config-refus","canonical_anchor":"auto-mode-rule-attribution-and-untrusted-folder-config-refus","heading":"Auto mode decisions can name the rule behind them and flag untrusted folders","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/auto-mode-rule-attribution-and-untrusted-folder-config-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Auto mode decisions can name the rule behind them and flag untrusted folders\n\nAuto mode results can now name the allow or soft deny rule that applied, and a permission check can now report an untrusted folder\n\n**Unclear.** Which folders count as untrusted, and exactly what Claude Code does with settings from them, is not stated.\n\n**What**\n\nWhen auto mode, which lets Claude act without asking you each time, makes a decision, the result can now carry the rule that applied: which list it came from (`allow` or `soft_deny`) and the rule's name.\n\nSeparately, when Claude Code checks where a permission setting came from, it can now answer `untrusted_folder`. Before, the only answers were managed rules only or your personal configuration.\n\n**Why**\n\nConfiguration that comes from a folder Claude Code does not trust can now be singled out instead of being treated like your own settings.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}