A stale local file can no longer keep auto mode switched off; startup re-checks the server.
What's wrong with this entry?
If the cached auto mode configuration said disabled and that value came from disk rather than a live override or server payload, it is now read back as enabled, and startup re-checks the killswitch against the remote config service before deciding. A stale local file can no longer keep auto mode switched off indefinitely.
- Two new startup awaits: initialising the remote config before mode selection, and the killswitch recheck itself, timed as
growthbook_killswitch_recheck_ms. - Only values sourced from an explicit override or a server payload are still honoured as disabling.
growthbook_killswitch_recheck_ms
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