{"version":"2.1.288","anchor":"growthbook-warm-cache-kick-can-be-forced-by-env-var","canonical_anchor":"growthbook-warm-cache-kick-can-be-forced-by-env-var","heading":"New environment variable forces an early feature-flag refresh in non-interactive runs","tier":"use","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/growthbook-warm-cache-kick-can-be-forced-by-env-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### New environment variable forces an early feature-flag refresh in non-interactive runs\n\nSetting `CLAUDE_CODE_GROWTHBOOK_KICK_ON_WARM_CACHE` makes non-interactive runs refresh feature flags early even with a saved copy\n\n**Unclear.** It is not clear exactly what the early refresh changes later in the run.\n\n**What**\n\nClaude Code fetches feature flags, settings Anthropic uses to switch features on and off, from a server, and keeps a saved copy between runs. At startup it decides whether to refresh them early. In non-interactive mode, where Claude Code runs a single request without the chat interface, setting `CLAUDE_CODE_GROWTHBOOK_KICK_ON_WARM_CACHE` now forces that early refresh even when a saved copy exists and the usual check would skip it.\n\n**Why**\n\nIt gives a way to make headless runs pick up current feature flags right away instead of relying on the saved copy.\n\n- Area: Internals\n- Names: `CLAUDE_CODE_GROWTHBOOK_KICK_ON_WARM_CACHE`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}