Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Startup now decides whether and when to fetch feature flags

Claude Code now decides at startup whether to fetch feature flags early, later or not at all, and briefly holds plugin hooks for one flag

Under the hood Internal Changes
JSON All of v2.1.288
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.288,
Internal ChangesSection of the release
What

Feature flags are switches the server uses to turn features on or off. At startup, Claude Code used to check whether the launch was eligible and then always fetch these flags. It now sorts each launch into a status first and only fetches flags for some statuses:

  • Not eligible.
  • Not asked, because the flags are already warm.
  • Settings still pending.
  • Started during startup, or started just after it.
  • Excluded for this launch.

Claude Code fetches flags only when the status is started during or after startup. Another new step briefly holds the hooks of installed plugins while it waits for a rollout flag, and records how long that wait took. A hook is code a plugin runs automatically at set moments.

Why

This changes when feature flags load at startup, especially for runs where nobody is typing.

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 doubtIt is not clear what `CLAUDE_CODE_GROWTHBOOK_KICK_FROM_INIT` does or which switch controls the wait on plugin hooks.

See this entry in the whole of v2.1.288 →

Feedback