Auto mode no longer needs CLAUDE_CODE_ENABLE_AUTO_MODE; setting it now does nothing at all.
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.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
2.1.247 refused auto mode on non-first-party providers with "auto mode requires CLAUDE_CODE_ENABLE_AUTO_MODE=1". That check is gone. The variable now survives only as a name in the environment-variable registry and is read nowhere in this build, so setting it does nothing. Auto mode can now be turned off by the disableAutoMode setting, by the remote tengu_auto_mode_config (built-in default enabled), by model support, or by the new fast-mode breaker.
- The fast-mode breaker surfaces to you as "auto mode unavailable while fast mode is on ยท run /fast off".
auto mode unavailable while fast mode is on \xB7 run /fast off
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.221
Auto mode exit message is tailored, and subagents no longer get it
Both mention auto mode
-
v2.1.229
Auto-mode setup confirmation is now a single keyboard form
Both mention auto mode