Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

API error categories renamed in logs and model-fallback suggestions

Error categories used for model-fallback suggestions and logging have new names, and running out of retry attempts is now logged too

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

Claude Code sorts failed requests to the API into categories. It uses them to decide whether suggesting a different model might help, and it records them in its usage data. Several of these names have changed:

  • unreachable is now noResponse.
  • refused is now httpError.
  • anotherModelCouldHelp is now fallbackModelCouldHelp.
  • connection is now connectionLost.
  • rejected is now badRequest.
  • unrecognised is now unknown.
  • watchdog is now stalled.
  • denied is a category that is now checked first.

The error logged after retries are used up now also covers the case no_api_attempts_left. The check for a rate limit error now compares the correct value.

Why

Anything that reads these logged values will see the new names instead of the old ones. The corrected rate limit check means that case is recognised as intended.

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 doubtIt is not clear what reads these renamed categories apart from Claude Code's own logging.

See this entry in the whole of v2.1.286 →

Feedback