{"version":"2.1.323","anchor":"feature-flag-cache-config-gains-savestakes-only-hooks-and-e","canonical_anchor":"feature-flag-cache-config-gains-savestakes-only-hooks-and-e","heading":"Feature-flag caching and the override variable now behave differently in some modes","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/feature-flag-cache-config-gains-savestakes-only-hooks-and-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Feature-flag caching and the override variable now behave differently in some modes\n\nClaude Code changed when it saves fetched feature flags and when it honours `CLAUDE_INTERNAL_FC_OVERRIDES`\n\n**Unclear.** Which sessions now ignore `CLAUDE_INTERNAL_FC_OVERRIDES` or skip saving the config is not clear.\n\n**What**\n\nFeature flags are switches Claude Code receives from Anthropic's servers that turn features on or off. Claude Code changed how it stores and overrides them:\n\n- `CLAUDE_INTERNAL_FC_OVERRIDES`, an environment variable (a named value set outside Claude Code), is now ignored under certain conditions. Before, it was always read.\n\n- The global configuration file is now saved under a different condition than before.\n\n- How fetched flags are saved and taken in has new controls.\n\n**Why**\n\nIf you set `CLAUDE_INTERNAL_FC_OVERRIDES` to change flag behaviour, it may no longer take effect in every session.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}