{"version":"2.1.323","anchor":"cached-feature-flags-and-training-consent-timestamp-added-to","canonical_anchor":"feature-flag-cache-renamed-to-cachedfeatureflags","heading":"Saved feature flag cache moves to cachedFeatureFlags","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/cached-feature-flags-and-training-consent-timestamp-added-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Saved feature flag cache moves to cachedFeatureFlags\n\nClaude Code now saves its feature flag cache under cachedFeatureFlags and cachedFeatureFlagsAt, and adds a trainingConsentSettledAt config key\n\n**What**\n\nFeature 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.\n\n- The saved flags are now written to `cachedFeatureFlags`, with the save time in `cachedFeatureFlagsAt`. Before, they were saved under `cachedGrowthBookFeatures`.\n\n- The old keys are kept only if they already exist in your config.\n\n- Saving is skipped when the flag client was created before you trusted the folder, when it only takes flags, or when `savesFetchedFlags` is false.\n\n- The list of saved global config keys now includes `cachedFeatureFlags`, `cachedFeatureFlagsAt` and a new `trainingConsentSettledAt`, alongside the existing `cachedGrowthBookFeatures`.\n\n**Why**\n\nYour 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.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}