{"version":"2.1.287","anchor":"startup-growthbook-refresh-can-be-kicked-early-via-new-env-v","canonical_anchor":"startup-growthbook-refresh-can-be-kicked-early-via-new-env-v","heading":"New environment variable starts the feature-flag refresh earlier in startup","tier":"use","area":"Startup","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/startup-growthbook-refresh-can-be-kicked-early-via-new-env-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### New environment variable starts the feature-flag refresh earlier in startup\n\nSetting CLAUDE_CODE_GROWTHBOOK_KICK_FROM_INIT lets Claude Code begin its feature-flag refresh during startup instead of after it\n\n**Unclear.** It is not clear exactly when during setup the early refresh is triggered.\n\n**What**\n\nWhen it starts, Claude Code refreshes its feature flags, which are server-controlled settings that switch features on and off. If you set the environment variable `CLAUDE_CODE_GROWTHBOOK_KICK_FROM_INIT`, this refresh step can now start from within the startup setup itself.\n\nIf the variable is not set, the step runs after setup, as before. The step is protected so it runs exactly once.\n\n**Why**\n\nStarting the refresh earlier may change how quickly fresh feature settings arrive and how long startup takes.\n\n- Area: Startup\n- Names: `CLAUDE_CODE_GROWTHBOOK_KICK_FROM_INIT`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}