Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

New tengu_sorted_flute gate can suppress local flag-settings writes

A new internal check can now silently skip saving flag settings changes to disk

Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release

Unclear 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 guard is meant to solve.

What

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_flute gate (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.

Why

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.

Read from
Feature flag
tengu_sorted_flute Not enough to say

Nothing 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

What has happened since
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_sorted_flute, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_sorted_flute, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_sorted_flute, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNothing 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…
The name it cites is new in this buildNew in this build: tengu_sorted_flute

See this entry in the whole of v2.1.280 →

Feedback