Auto mode can be disabled server-side while /fast is on, but nothing sets that today.
A disableFastMode breaker exists with no local default, so it never fires without server config.
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?
A new circuit breaker disables auto mode with the reason "fast-mode" when the remote tengu_auto_mode_config object sets disableFastMode and you have /fast toggled on. There is no local fallback value for disableFastMode, so with no server config it is undefined and the breaker never fires. This replaces the old branch that blocked auto mode for providers lacking an opt-in.
- The debug output now reports a
disableFastModeBreakerFirescounter.
auto mode disabled: tengu_auto_mode_config.disableFastMode with the /fast toggle 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.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
-
v2.1.229
Auto-mode setup wizard reduced to one screen
Both mention auto mode