autoMode
A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
Add your own allow and deny rules to the auto mode classifier
Anthropic's own wording. Read off All settings, captured 2026-11-12.
In the changelogs
17Releases whose published page names autoMode.
-
v2.1.321
Settings changes that only restrict autoMode rules are marked separately
When a settings change restricts permissions, Claude Code now notes whether the only restricting key is autoMode with allow or environment entries
found in this entry's text, named in this entry
-
v2.1.321
Cloud sessions now refuse auto mode rules from settings files
A cloud session given an autoMode block through --settings or a repository's .claude/settings.json now stops with an error
found in this entry's text, named in this entry
-
v2.1.319
SDK results can name the auto mode rule behind a decision
Results reported through the SDK now have a field naming which of your own auto mode rules decided a tool call
found in this entry's text, named in this entry
-
v2.1.319
Auto mode explains when your rules are too large to use
Auto mode now turns itself off with an explanation when your permission rules and
autoModesettings total more than about 1 MBfound in this entry's text, named in this entry
-
v2.1.315
Auto mode allow rules are combined per settings source
Auto mode allow rules are now gathered per settings source, and command-line allow rules are merged with managed policy
found in this entry's text, named in this entry
-
v2.1.295
Self-hosted runners can pass server-supplied auto mode rules into sessions
A self-hosted runner can write auto mode allow and deny lists from the server into a session's settings, with allow lists held back by default
found in this entry's text, named in this entry
-
v2.1.283
One invalid sandbox deny entry now withholds the matching allow rules
If one entry in deniedDomains, denyWrite or denyRead is invalid, Claude Code now withholds the matching allow list instead of applying it
found in this entry's text
-
v2.1.282
Broken managed settings now fail safe, including permission and sandbox blocks
An invalid value in managed settings now becomes its most restrictive value, and a block with an unreadable deny rule loses its allow grants
named in this entry, found in this entry's text
-
v2.1.248
Auto-mode and import subcommands moved
Some auth and auto subcommands moved to a different command object with unchanged behaviour.
found in this entry's text
-
v2.1.212
Auto-mode Setup (/auto-mode-setup)
found in this entry's text
-
v2.1.207
/auto-mode-setup: Expanded Rule Audit
found in this entry's text
-
v2.1.207
Auto Mode Settings Locked to Trusted Sources
found in this entry's text
-
v2.1.207
/auto-mode-setup: project settings.local.json Audit
found in this entry's text
-
v2.1.136
Auto Mode Hard-Deny Rules
found in this entry's text
-
v2.1.108
Assistant Feature Gate [In Development]
found in this entry's text
-
v2.1.108
Settings Schema Refactored to Feature Gates
found in this entry's text
-
v2.1.81
Auto Mode Rule Critique CLI
found in this entry's text
First cited
4The earliest release whose published evidence quoted autoMode was v2.1.136, 8 May 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.