{"version":"2.1.285","anchor":"startup-growthbook-wait-decision-refactored","canonical_anchor":"startup-growthbook-wait-decision-refactored","heading":"Startup wait for feature settings reorganised and now recorded","tier":"internal","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/startup-growthbook-wait-decision-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Startup wait for feature settings reorganised and now recorded\n\nHow Claude Code decides whether to wait for feature settings at startup was reorganised, and the wait is now recorded\n\n**Unclear.** It is unclear whether how long startup waits has itself changed.\n\n**What**\n\nAt startup Claude Code may wait for feature flags, remote switches that turn parts of it on or off. The decision to wait changed: it now comes from shared checks that consider the time available, whether settings are still pending, whether a saved copy is empty, and whether an early fetch was started. The old decision and the recheck for switched-off features remain, and the wait is now recorded in Claude Code's usage data.\n\n**Why**\n\nThe main visible difference is in what gets recorded about the startup wait.\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}