Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

New env var CLAUDE_CODE_FLAG_FETCH_WAIT_MS controls a start-up wait for GrowthBook flags on relaunch

New CLAUDE_CODE_FLAG_FETCH_WAIT_MS env var sets how long startup waits for feature flags on relaunch

TierUse it nowhow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaStartupwhat it touches
KindNew Featuresin v2.1.269,
Use it now Notable No documentation found

New CLAUDE_CODE_FLAG_FETCH_WAIT_MS env var sets how long startup waits for feature flags on relaunch

What

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

Why

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

Read from
Names in the bundleCLAUDE_CODE_FLAG_FETCH_WAIT_MS
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what happens differently if the wait times out versus succeeds.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_FLAG_FETCH_WAIT_MS

See this entry in the whole of v2.1.269 →