Follow Discord
Sweep 12 Nov 2026 · 20:38Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.322 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
The last run did not finish v2.1.323 no changelog was produced for this release

Claude Code v2.1.281 ·

API error kind: some errors lose the _no_retry suffix; new 503 no-retry helper

Some API errors are now labelled plain http_<status> without the _no_retry suffix, and 503 no-retry responses get their own check

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

Unclear The finding does not say what the internal check tests or where the new 503 helper is used.

What

When a request to the API fails, Claude Code labels the error by its HTTP status, adding _no_retry when the server's x-should-retry header says not to retry. When a certain internal check returns a value, the label is now plain http_${status} even if x-should-retry is false. A new helper matches status 503 (service unavailable) with x-should-retry set to "false".

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 doubtThe finding does not say what the internal check tests or where the new 503 helper is used.

See this entry in the whole of v2.1.281 →

Feedback