{"version":"2.1.269","anchor":"new-env-var-claude-code-flag-fetch-wait-ms-controls-a-start","canonical_anchor":"new-env-var-claude-code-flag-fetch-wait-ms-controls-a-start","heading":"New env var CLAUDE_CODE_FLAG_FETCH_WAIT_MS controls a start-up wait for GrowthBook flags on relaunch","tier":"use","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-env-var-claude-code-flag-fetch-wait-ms-controls-a-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New env var CLAUDE_CODE_FLAG_FETCH_WAIT_MS controls a start-up wait for GrowthBook flags on relaunch\n\nNew CLAUDE_CODE_FLAG_FETCH_WAIT_MS env var sets how long startup waits for feature flags on relaunch\n\n**Unclear.** The finding does not say what happens differently if the wait times out versus succeeds.\n\n**What**\n\nA new environment variable, `CLAUDE_CODE_FLAG_FETCH_WAIT_MS`, controls how long Claude Code will wait at startup for its feature flags (fetched via GrowthBook) to load when the session is a relaunch. If unset, it defaults to 3000 milliseconds. Startup also separately waits a fixed amount if event logging is enabled and its cache is empty. The relaunch condition itself is limited to cases involving `CLAUDE_CODE_REMOTE`.\n\n**Why**\n\nThis gives more control over the tradeoff between startup speed and having up-to-date feature flags immediately available when a session relaunches, and Claude Code now reports whether that wait timed out.\n\n- Area: Startup\n- Names: `CLAUDE_CODE_FLAG_FETCH_WAIT_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}