If your org's settings ban auto mode here, Claude Code exits it and tells you why.
tengu_auto_mode_config Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.251: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
If your organization's managed settings disable auto mode for the kind of session you are in, Claude Code now leaves auto mode during its normal permission refresh and posts a notice in the conversation pointing at settings, rather than staying in a mode policy forbids.
- Triggers when the current mode is auto, or plan with auto queued up behind it, and the managed policy check says auto is not allowed here.
- Skipped when admin policy settings failed to load with a non-warning error, unless the admin-survivor fallback is active.
- Auto mode itself is controlled by the
tengu_auto_mode_configgate, which resolves to enabled when the server sends no value.
exitedAutoMode
Strings lifted out of the shipped bundle, so the claim above can be checked against them.