{"version":"2.1.269","anchor":"auto-mode-classifier-growthbook-init-call-carries-cachetel","canonical_anchor":"auto-mode-classifier-growthbook-init-call-carries-cachetel","heading":"Auto-mode classifier: GrowthBook init call carries cache\/telemetry params","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/auto-mode-classifier-growthbook-init-call-carries-cachetel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Auto-mode classifier: GrowthBook init call carries cache\/telemetry params\n\nAuto-mode's GrowthBook setup call now passes caching and telemetry parameters and reuses its result\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis avoids redundant initialization work during auto-mode setup by reusing a result that was already computed instead of repeating the call.\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.269; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}