Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.179 Home All releases olderv2.1.178 v2.1.181newer
Claude Code v2.1.179

Better Messages When API Connection Drops

Three new user-facing messages now appear when a streaming connection is lost:

  • Mid-response (after some content was already delivered): Connection closed mid-response. The response above may be incomplete.
  • During thinking (before any content): Connection closed while thinking, before producing a response. Try again.
  • Network-level errors (ECONNRESET, EPIPE, etc.): Connection to the API was lost (<error_code>). This is usually temporary — try again.

Previously these all surfaced as generic error messages.

Evidence

Stream-drop messages (search for "Connection closed mid-response" and "Connection closed while thinking") and network-error handler (search for "Connection to the API was lost (")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.179 →