What
Claude 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.
Details
- Both spellings are checked, so the key works at the top level of settings or nested under
permissions. - The resolver's result now also reports a
baselineMode(the mode it started from before any fallback) alongside the mode it settled on. - A proactivity level is now passed into the resolver and a
decidedByProactivityLevelflag returned with it, but that flag is always false here and the resolver'sproactivityoutput is undefined, so proactivity does not influence the chosen mode in this build.
Usage
{ "permissions": { "disableAutoMode": "disable" } }Evidence
decidedByProactivityLevel
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundledisableAutoModepermissions.disableAutoMode