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 ·

'Ask seat' remote-tool waiting now controlled by an environment-variable override and feature gates

Whether tool calls wait for remote approval capacity is now controlled by CLAUDE_CODE_REMOTE_TOOLS_ASK_SEATS and new feature gates

Group of 2 Use it now Internal Changes
JSON All of v2.1.280
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.280,
What probably matters to youSection of the release

Unclear What tengu_unified_waterfall and tengu_violin_speculative_classifier actually enable is not stated, and neither gate's on/off state for this release is known.

What

  • The function that decides whether tool calls wait on an "ask seat" (a unit of remote approval capacity) now reads the CLAUDE_CODE_REMOTE_TOOLS_ASK_SEATS environment variable as an override, falling back to a feature gate named tengu_unified_waterfall, which defaults to true.
  • A second new gate, tengu_violin_speculative_classifier, was also added, but it is currently wired to a function that always returns false, meaning it exists in the code but is not yet active.

Why This gives more explicit control over remote tool-approval waiting behavior and lays groundwork for a speculative classifier feature that is not turned on yet.

Read from
Feature flag
tengu_unified_waterfall 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: on

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.

tengu_violin_speculative_classifier Gate removed from the code

This release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.

This account: on · anonymous baseline: on · compiled default in v2.1.280: 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.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 off for tengu_violin_speculative_classifier, 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.
Gate removed from the code v2.1.280 removed the tengu_violin_speculative_classifier gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.

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 doubtWhat tengu_unified_waterfall and tengu_violin_speculative_classifier actually enable is not stated, and neither gate's on/off state for this…
The name it cites is new in this buildNew in this build: tengu_unified_waterfall

See this entry in the whole of v2.1.280 →

Feedback