Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

A turn that ends on an API error now goes through the normal stop handling

When the last message in a turn is an API error, Claude Code now runs its usual end-of-turn stop handling

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

Unclear What the stop handling actually does for you when a turn ends on an API error is not stated.

What

When a turn ends, Claude Code checks whether it should run its stop handling, the steps it takes once the model has stopped. It now also runs that handling when the last message is an API error, meaning an error that came back from Anthropic's service instead of a normal reply. Before, an API error at the end of a turn did not count on its own.

Claude Code also now records that the model stopped, noting that this did not happen through the keepalive path, which is the mechanism that keeps a session going between turns.

Why

This changes what Claude Code does at the end of a turn that fails with an API error.

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 doubtWhat the stop handling actually does for you when a turn ends on an API error is not stated.

See this entry in the whole of v2.1.319 →

Feedback