{"version":"2.1.269","anchor":"new-startup-telemetry-for-feature-flag-growthbook-fetch-wa","canonical_anchor":"new-startup-telemetry-for-feature-flag-growthbook-fetch-wa","heading":"New startup telemetry for feature-flag (growthbook) fetch waits","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-startup-telemetry-for-feature-flag-growthbook-fetch-wa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New startup telemetry for feature-flag (growthbook) fetch waits\n\nNew telemetry tracks how long startup waits on remote feature-flag fetches\n\n**What**\n\nClaude Code's startup process now records a `tengu_startup_flag_fetch_wait` telemetry event whenever it waits on fetching remote feature flags (settings that turn features on or off remotely, via a service called GrowthBook). The event notes where the wait happened (before tools are set up, or before context is set up), how long it waited, and whether the wait timed out.\n\n**Why**\n\nThis gives visibility into how much startup time is spent waiting on remote flag fetches, which can help identify and address startup slowness caused by that step.\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}