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 ·

A secure-connection error partway through a reply is handled as a cut-off reply

If a secure-connection error hits after a reply has started arriving, Claude Code now treats it the same as a reply that was cut short

You'll notice Bug Fixes
JSON All of v2.1.321
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
StreamingArea: what it touches
Bug FixesKind: in v2.1.321,
Bug FixesSection of the release

Unclear Whether a reply cut off this way is now retried automatically is not known.

What

The model's reply arrives in pieces, as a stream. If the secure (TLS) connection fails after at least one piece has arrived, Claude Code now logs the error and treats it as a stream that was cut short. Its usual handling for cut-off replies then applies.

Why

A connection reset in the middle of a reply is now handled the same way as any other interrupted reply, instead of as a separate kind of failure.

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 doubtWhether a reply cut off this way is now retried automatically is not known.

See this entry in the whole of v2.1.321 →

Feedback