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

Interrupted replies can retry after a wait, with separate timing when overloaded

When a reply is cut off by a server error, Claude Code can wait before retrying; this is off unless switched on remotely

You'll notice Improvements
JSON All of v2.1.321
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
NetworkArea: what it touches
ImprovementsKind: in v2.1.321,
ImprovementsSection of the release
What

When a reply from the server is cut off partway by a server error, Claude Code can now work out how long to wait before trying again. When the error says the server is overloaded, the wait can follow:

If the wait cannot be set up, Claude Code retries with no wait. This whole behaviour is off unless it is switched on remotely.

Why

When it is switched on, a cut-off reply is retried after a pause rather than failing outright, which gives a busy server time to recover.

Read from
Feature flag
tengu_dreamy_flute Off in both readings

The 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.321: 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.321. It isn't a statement about your account. What a flag value here can and cannot tell you

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_dreamy_flute

See this entry in the whole of v2.1.321 →

Feedback