Auto mode uses sensible built-in defaults when remote config is missing, instead of everything off.
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.236: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Auto mode used to read an empty config, meaning every option off, whenever the remote config key tengu_auto_mode_config was missing. All readers now go through one helper that applies a frozen built-in default instead. This only kicks in when the key is absent and GrowthBook is unavailable or DISABLE_GROWTHBOOK is set.
- Defaults on: two-stage classifier, same-turn sibling context, JSONL transcript, edit-removal visibility (capped at 3000), repo visibility, git status type.
- Defaults off: outcome visibility, git status uploads.
- Per-model severity thresholds ship as part of the same default.
tengu_auto_mode_config
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.
-
v2.1.232
disableAutoModesetting can switch off the auto permission mode fallbackBoth mention disable auto mode
-
v2.1.248
CLAUDE_CODE_ENABLE_AUTO_MODE is no longer required, or read at all
Both mention disable auto mode
-
v2.1.221
Auto mode exit message is tailored, and subagents no longer get it
Both mention auto mode