Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

disableAutoMode setting can switch off the auto permission mode fallback

Use it now
Useful4 Signal3
Permissions Notable

Set disableAutoMode to "disable" to stop Claude Code ever falling back to auto permission mode.

disableAutoModepermissions.disableAutoMode
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 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.
Usage
{ "permissions": { "disableAutoMode": "disable" } }
Evidence

decidedByProactivityLevel

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →