Auto-mode's GrowthBook setup call now passes caching and telemetry parameters and reuses its result
The GrowthBook (feature flag/experiment) initialization call made before auto-mode's classification loop starts now builds a parameters object first, passing along whether event logging is enabled, whether GrowthBook itself is enabled, whether the cache is empty, and a relaunch counter. Its result is now stored rather than discarded, and a later recheck of the auto-mode kill switch checks whether that stored result already exists before redoing the work.
This avoids redundant initialization work during auto-mode setup by reusing a result that was already computed instead of repeating the call.
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.269: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you