{"version":"2.1.232","anchor":"disableautomode-setting-can-switch-off-the-auto-permission-m","canonical_anchor":"disableautomode-setting-can-switch-off-the-auto-permission-m","heading":"disableAutoMode setting can switch off the auto permission mode fallback","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/disableautomode-setting-can-switch-off-the-auto-permission-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### `disableAutoMode` setting can switch off the auto permission mode fallback\n\nSet `disableAutoMode` to \"disable\" to stop Claude Code ever falling back to auto permission mode.\n\n**What**\n\nClaude Code will no longer fall back to auto mode if either `permissions.disableAutoMode` or the top-level `disableAutoMode` setting is set to `\"disable\"`. The fallback also still requires the auto-mode circuit breaker to be inactive and remote config to allow auto mode, so setting neither key leaves behaviour as before.\n\n**Details**\n\n- Both spellings are checked, so the key works at the top level of settings or nested under `permissions`.\n- The resolver's result now also reports a `baselineMode` (the mode it started from before any fallback) alongside the mode it settled on.\n- A proactivity level is now passed into the resolver and a `decidedByProactivityLevel` flag returned with it, but that flag is always false here and the resolver's `proactivity` output is undefined, so proactivity does not influence the chosen mode in this build.\n\n**Usage**\n\n`{ \"permissions\": { \"disableAutoMode\": \"disable\" } }` **Evidence** `decidedByProactivityLevel`\n\n- Area: Permissions\n- Names: `disableAutoMode`, `permissions.disableAutoMode`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}