Claude Code has an internal function, apply_flag_settings, that saves merged settings to disk and tells other parts of the app about the change. Previously it always did both of those things. Now, under a new condition, it can skip saving and notifying entirely:
- the settings being applied are unchanged from what's already stored
- the new
tengu_sorted_flutegate (an internal switch Anthropic can turn on or off remotely) is on - a guard function supplied by the calling code returns false
When all three are true, the write and notification are suppressed.
This looks like a guard against unnecessary disk writes when nothing has actually changed, letting a caller opt out of a redundant save-and-notify cycle. If you notice a settings change not taking effect or not triggering an update you expected, this new skip path is a place to look.
tengu_sorted_flute Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.280: off
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.280. It isn't a statement about your account. What a flag value here can and cannot tell you
Nothing has been read yet about whether tengu_sorted_flute is on or off by default, and the finding does not say what practical problem this…
New in this build: tengu_sorted_flute