Claude Code can skip saving flag settings, and skip telling the rest of the app about them, when nothing has changed. That skip used to depend in part on a switch Anthropic controls from its servers. The switch was off unless the server sent a value.
That remote switch no longer plays a part. The skip now depends on these things:
- How Claude Code was started, read from the
CLAUDE_CODE_ENTRYPOINTenvironment variable. - A policy setting, which appears to relate to managed permission rules set by an administrator.
- The same unchanged-settings check and caller check as before.
Whether this skip happens is now decided by the local environment and policy rather than by Anthropic remotely. That makes the behaviour easier to predict from your own setup.
tengu_sorted_flute Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.286: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.286. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not certain which launch mode and which policy setting the new conditions check.