Omniscio

OmniscioGuidesThe response above may be incomplete

The response above may be incomplete: what was kept, and how to carry on

Last checked against Anthropic's documentation on November 20, 2026. By the Omniscio team. Updated .

What are the exact messages?

There is one notice and six ways to reach it. Anthropic prints them like this:

API Error: Server error mid-response. The response above may be incomplete.
API Error: Connection lost mid-response. The response above may be incomplete.
API Error: Your computer went to sleep mid-response. The response above may be incomplete.
API Error: The response stopped arriving. The response above may be incomplete.
API Error: Part of the response never arrived. The response above may be incomplete.
API Error: The response stream was malformed. The response above may be incomplete.

Two of these were worded differently before v2.1.227, so older sessions and older screenshots read Connection closed mid-response instead of Connection lost mid-response, and Response stalled mid-stream instead of The response stopped arriving.

What does it mean?

A streaming request failed while the response was still in progress, after Claude had completed a block of text or a tool call, or had started one after finishing its thinking.

Anthropic's reason for not retrying is the useful part: re-sending the request could run the same tool calls twice. So Claude Code keeps the output Claude completed and appends this notice instead of discarding the turn. You are looking at a partial answer that is kept on purpose, not a failed one.

One scope note matters. For a dropped, duplicated or damaged stream event that arrives before Claude has started any text or tool call, the notice is not shown at all. If only its thinking had completed, Claude Code re-issues the request; if the re-issued streams break the same way, the turn ends with Part of the response never arrived and no response was produced. Try again. or The response stream was malformed and no response was produced. Try again. instead.

A tool call that had already finished ran, and its result is part of what was kept. That is exactly why the request is not re-sent: repeating it could run the same call twice. Anthropic's wording for what is lost is that the final sentences or tool calls may be missing, so if a call was in flight when the stream broke, check whether it actually ran before asking Claude to do that step again.

What each variant names

  • Server error mid-response: a mid-stream overloaded or 5xx server error.
  • Connection lost mid-response: the connection dropped. Anthropic notes you also see this variant when a proxy or gateway ends the response body cleanly before the response has finished.
  • Your computer went to sleep mid-response: Claude Code detected that the computer slept while the response was streaming. Once it wakes, Claude Code treats the connection as broken and stops reading from it.
  • The response stopped arriving: the connection stayed open but stopped delivering data, so the streaming idle watchdog aborted it.
  • Part of the response never arrived: a stream event was dropped between the API and Claude Code, so a later event referenced content that never arrived.
  • The response stream was malformed: an event arrived for a content block that had already finished, or an event arrived damaged — data that isn't valid JSON, content that is missing, or content that doesn't match the event's type.

How do I fix it?

  1. In an interactive session, reply continue. Claude picks up from its last completed block. Read what is on screen first: every block Claude completed is kept, but an interrupted final block is discarded when the turn ends.
  2. In a -p run, resume the session and send continue. With the default text output Claude Code prints the last completed block of text it still holds, followed by the notice; when it holds none, the notice appears alone.
  3. In a --output-format json or stream-json run, read the result field. Anthropic reports the notice there rather than on standard output.
  4. If it keeps happening, look at the hop. A proxy or gateway that ends the body early is the documented cause of the connection-lost variant; the checks are on the connection errors page.

Do I have to continue it myself?

In a non-interactive session — a -p run, an Agent SDK run, or a cloud session — not always. When the cut-off response is in the main conversation and contains text but no tool calls, Anthropic documents that Claude Code keeps the partial output and prompts Claude to continue from where it stopped, up to three times in a row. You see the notice only once those continuations are used up.

A subagent is handled the same way, whether the session is interactive or not: when its cut-off response contains text but no tool calls, Claude Code prompts the subagent to continue, and the notice becomes the subagent's last message only once those continuations are used up.

How do I know it is fixed?

  • After continue, the reply carries on from the last completed block instead of starting over.
  • Later turns finish without the notice, so the hop between Claude Code and the provider is passing a whole stream again.
  • In a -p run, the result field holds a real answer rather than the notice.

Where these answers come from

  • All six variants, what each names, the reason a re-send is refused, the older wordings, the cases where no notice appears, the interactive and non-interactive steps and the continuation counts for a non-interactive session and a subagent: Anthropic's error reference, read November 20, 2026.
  • What is retried and what is deliberately not retried mid-response: Anthropic's automatic retries section, read November 20, 2026.
  • The stall that produces the stopped-arriving variant: Anthropic's streaming idle watchdogs, read November 20, 2026.

Common questions

Why did Claude Code keep half an answer instead of trying again?

Because re-sending could run the same tool calls twice. Anthropic documents that Claude Code keeps the output Claude completed and appends the notice instead of discarding the turn.

What should I type?

In an interactive session, reply with continue. Anthropic documents that Claude Code keeps every block Claude completed but discards an interrupted final block when the turn ends, so the last sentences or tool calls may be missing.

Which of the six variants do I have?

The words after API Error name it: Server error mid-response, Connection lost mid-response, Your computer went to sleep mid-response, The response stopped arriving, Part of the response never arrived, or The response stream was malformed. Each names a different cause of the same cut-off.

Do I need to do anything in a -p run?

Not always. Anthropic documents that in a non-interactive session, when the cut-off response is in the main conversation and contains text but no tool calls, Claude Code prompts Claude to continue up to three times in a row before the notice appears.

Did the tool calls that already ran still count?

Yes. Anthropic documents that Claude Code keeps what Claude completed, runs any tool calls Claude finished, and continues the turn from their results. The call that was in flight when the stream broke is the one that has no result.