Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.323entry #683

Claude Code v2.1.323 ·

Saved feature flag cache moves to cachedFeatureFlags

Claude Code now saves its feature flag cache under cachedFeatureFlags and cachedFeatureFlagsAt, and adds a trainingConsentSettledAt config key

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

What

Feature flags are switches that turn parts of Claude Code on or off remotely, and Claude Code keeps a copy of them in its global config file. That copy has moved to new keys.

  • The saved flags are now written to cachedFeatureFlags, with the save time in cachedFeatureFlagsAt. Before, they were saved under cachedGrowthBookFeatures.
  • The old keys are kept only if they already exist in your config.
  • Saving is skipped when the flag client was created before you trusted the folder, when it only takes flags, or when savesFetchedFlags is false.
  • The list of saved global config keys now includes cachedFeatureFlags, cachedFeatureFlagsAt and a new trainingConsentSettledAt, alongside the existing cachedGrowthBookFeatures.

Why

Your config file gains new keys. Because the old keys stay when they are already present, an older version of Claude Code can still find its flag cache if you go back to it. trainingConsentSettledAt appears to record a training-consent state, though the members do not show how it is used.

Read from
Names in the bundlecachedFeatureFlagscachedFeatureFlagsAtcachedGrowthBookFeatures

See this entry in the whole of v2.1.323 →

Feedback