{"version":"2.1.315","anchor":"statsig-style-flag-store-skipped-in-some-mode","canonical_anchor":"statsig-style-flag-store-skipped-in-some-mode","heading":"Feature flag settings are not saved in one mode","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/statsig-style-flag-store-skipped-in-some-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Feature flag settings are not saved in one mode\n\nIn one mode, Claude Code no longer saves feature flag settings to its config or logs which flags were used\n\n**Unclear.** It is not clear which mode turns this off, so readers cannot tell when it applies to them.\n\n**What**\n\nClaude Code stores feature flag values in its global config and records when a flag is checked. In one mode, it now skips both.\n\n**Why**\n\nThis may be a read-only mode where Claude Code avoids writing to disk or reporting flag use.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}