New environment variables to trigger a feature-flag refresh

Use it now Notable New Features

JSON All of v2.1.323

Use it nowTier: how much it should matter to you

4Useful: my rating, 1 to 5

3Signal: worth watching, 1 to 5

InternalsArea: what it touches

New FeaturesKind: in v2.1.323, 12 Nov 26

What probably matters to youSection of the release

What

Claude Code reads feature-flag settings from a server. Two new environment variables can trigger a refresh of those settings:

CLAUDE_CODE_FEATURE_FLAGS_KICK_FROM_INIT triggers it at startup.
CLAUDE_CODE_FEATURE_FLAGS_KICK_ON_WARM_CACHE triggers it when a saved copy already exists.

The older CLAUDE_CODE_GROWTHBOOK_KICK_* names still work. Setting either the old or the new name is enough.

Why

The 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.

See this entry in the whole of v2.1.323 →

The build it came inv2.1.323

12 Nov 2026 · 888 entries, this one is #42.

Use it now77
You'll notice533
Nothing to try yet64
Under the hood214

Either side of it

v2.1.322Older

Open the release →

Names in this entry

envCLAUDE_CODE_FEATURE_FLAGS_KICK_FROM_INIT
CLAUDE_CODE_FEATURE_FLAGS_KICK_FROM_INIT and CLAUDE_CODE_FEATURE_FLAGS_KICK_ON_WARM_CACHE join the older GrowthBook names, which still work
envCLAUDE_CODE_FEATURE_FLAGS_KICK_ON_WARM_CACHE
CLAUDE_CODE_FEATURE_FLAGS_KICK_FROM_INIT and CLAUDE_CODE_FEATURE_FLAGS_KICK_ON_WARM_CACHE join the older GrowthBook names, which still work

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.