{"version":"2.1.321","anchor":"settings-restricts-result-flags-automode-only-changes","canonical_anchor":"settings-restricts-result-flags-automode-only-changes","heading":"Settings changes that only restrict autoMode rules are marked separately","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/settings-restricts-result-flags-automode-only-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Settings changes that only restrict autoMode rules are marked separately\n\nWhen a settings change restricts permissions, Claude Code now notes whether the only restricting key is autoMode with allow or environment entries\n\n**Unclear.** What Claude Code does differently when a change only touches autoMode rules is not settled.\n\n**What**\n\nClaude Code sorts settings changes by their effect, and one kind is a change that restricts what Claude may do. That kind now also records whether the only restricting key is `autoMode`, the setting that adds your own allow and deny rules to the auto mode classifier. It does so when that key's entries are only allow rules, environment entries, or values that fail a further check.\n\n**Why**\n\nIt looks like changes limited to `autoMode` rules are treated differently when Claude Code decides whether to trust or approve settings.\n\n- Area: Settings\n- Names: `autoMode`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}