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.257 ·

tengu_fizzy_grove gate swaps the interrupt error code

A gate decides which of two error codes an interrupt-triggered abort reports.

Nothing to try yet No documentation found Internal Changes
JSON All of v2.1.257
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.257,
Internal ChangesSection of the release

On abort or interrupt, a helper now picks between two different error-code constants based on the tengu_fizzy_grove gate: when the gate is true and the abort reason is 'interrupt', a different constant is returned than on the default path. Multiple call sites already use this for turn-abort error reporting, so only the gate value decides which code ships.

Read from
Feature flag
tengu_fizzy_grove 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.257: 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.257. 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_fizzy_grove, 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_fizzy_grove, 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
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_fizzy_grove

See this entry in the whole of v2.1.257 →

Feedback