{"version":"2.1.285","anchor":"startup-flag-fetch-telemetry-adds-warm-wake-early-fetch","canonical_anchor":"startup-flag-fetch-telemetry-adds-warm-wake-early-fetch","heading":"Startup telemetry notes early feature-setting fetches on a warm wake","tier":"internal","area":"Startup","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/startup-flag-fetch-telemetry-adds-warm-wake-early-fetch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Startup telemetry notes early feature-setting fetches on a warm wake\n\nStartup telemetry for waits on remote feature settings now records whether the fetch started early on a warm wake\n\n**Unclear.** It is not clear what the tengu_cobalt_thicket gate itself controls.\n\n**What**\n\nThe `tengu_startup_flag_fetch_wait` telemetry event records how long Claude Code waits for remote feature settings at startup. It gains a `warm_wake_early_fetch` field. The data Claude Code prepares at startup also now notes whether a settings fetch made while Claude Code relaunched had finished.\n\nThis is tied to a remote gate, `tengu_cobalt_thicket`, which the code treats as on when the server sends nothing. The flag server has returned off for this site's account and for an anonymous check, in readings taken before this release.\n\n**Why**\n\nThis adds detail to the telemetry on the startup settings fetch. It does not change what you see.\n\n- Flag `tengu_cobalt_thicket`: Off in both readings (read for one account on one subscription tier against v2.1.285; this account: off, anonymous baseline: off, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}