{"version":"2.1.323","anchor":"feature-flag-refresh-can-be-kicked-from-init-or-warm-cache-v","canonical_anchor":"feature-flag-refresh-can-be-kicked-from-init-or-warm-cache-v","heading":"New environment variables to trigger a feature-flag refresh","tier":"use","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/feature-flag-refresh-can-be-kicked-from-init-or-warm-cache-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### New environment variables to trigger a feature-flag refresh\n\n`CLAUDE_CODE_FEATURE_FLAGS_KICK_FROM_INIT` and `CLAUDE_CODE_FEATURE_FLAGS_KICK_ON_WARM_CACHE` join the older GrowthBook names, which still work\n\n**What**\n\nClaude Code reads feature-flag settings from a server. Two new environment variables can trigger a refresh of those settings:\n\n- `CLAUDE_CODE_FEATURE_FLAGS_KICK_FROM_INIT` triggers it at startup.\n\n- `CLAUDE_CODE_FEATURE_FLAGS_KICK_ON_WARM_CACHE` triggers it when a saved copy already exists.\n\nThe older `CLAUDE_CODE_GROWTHBOOK_KICK_*` names still work. Setting either the old or the new name is enough.\n\n**Why**\n\nThe new names do not mention a particular flag service. If you already use the old names, nothing changes for you, and you can move to the new names at any time.\n\n- Area: Internals\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}