Non-interactive /auto-mode-setup now just needs a resolved model and no remote flag.
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.232: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The two forms of /auto-mode-setup now have separate availability. The interactive form still requires the envOnboarding field of the tengu_auto_mode_config remote setting to be on. The non-interactive form now only needs a resolved auto-mode model and CLAUDE_CODE_REMOTE to be unset. Previously both shared the gated check.
isEnabled: () => lRa() && On(),
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.229
Auto-mode setup rewritten around a single confirmation step
Both mention auto mode setup
-
v2.1.236
Auto mode setup prompt and copy rewritten
Both mention auto mode setup
-
v2.1.221
Auto mode exit message is tailored, and subagents no longer get it
Both mention auto mode