{"version":"2.1.318","anchor":"permission-classifier-uncertain-case-also-checks-settings","canonical_anchor":"permission-classifier-uncertain-case-also-checks-settings","heading":"Unclear actions that name settings files get flagged more often","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/permission-classifier-uncertain-case-also-checks-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Unclear actions that name settings files get flagged more often\n\nWhen the permission check can't decide, an action is now also flagged as touching settings if it matches a settings-file check\n\n**What**\n\nClaude Code has an automatic check that judges whether an action, such as a command, needs your permission. When that check is unsure, it can mark the action as naming settings. It used to do this only when a file-or-folder check matched. It now also does it when a separate check for settings files matches.\n\n**Why**\n\nMore unclear actions that touch settings files get flagged rather than passing quietly.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}