Omniscio

OmniscioGuidesStreaming response ended

Streaming response ended before any complete data was received

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

What is the exact message?

Streaming response ended before any complete data was received. Retrying without streaming. If this keeps happening, check any proxy or gateway between Claude Code and your model provider.

The first sentence is the failure. The second is the action Claude Code is already taking, so you do not need to retry anything yourself.

What does it mean?

A streaming response from your model provider completed without delivering any usable data, so Claude Code re-sent the request without streaming to finish the turn. The reply you end up with came from that second, non-streaming attempt.

Anthropic documents two details worth knowing. Claude Code sends each affected request twice — the empty streaming attempt and the retry — so a turn like this costs two requests. And the warning is shown once per session, in interactive sessions only; before v2.1.239 Claude Code silently retried without streaming and showed nothing at all.

What causes it

  • A proxy or gateway that rewrites the stream. Anthropic names a proxy or gateway that consumes or transforms the streaming response body on its way back as the usual cause. The request leaves fine; the reply is what gets damaged.
  • A gateway in front of Amazon Bedrock. Bedrock streams responses in a binary event-stream tagged application/vnd.amazon.eventstream. A gateway or proxy between Claude Code and Bedrock has to forward that body and its Content-Type header as Bedrock sent them. Claude Code rejects a response that reports a different content-type, and the common rewrite is text/event-stream, from an integration that re-emits the stream as server-sent events.
  • A gateway that is really something else. Anthropic's own wording: a gateway that converts the stream to server-sent events is no longer serving the Amazon Bedrock API. If it also accepts Anthropic Messages API requests, it should be connected as an LLM gateway with ANTHROPIC_BASE_URL instead of CLAUDE_CODE_USE_BEDROCK.

How do I fix it?

  1. First, find out whether anything is actually in the path. Claude Code takes its proxy from the environment, and Anthropic documents that it reads https_proxy, HTTPS_PROXY, http_proxy and HTTP_PROXY, using the first one that is set; a value in your settings file's env block is read too. So check all four and the settings file: env | grep -i proxy on macOS or Linux, Get-ChildItem Env:*proxy* in PowerShell. Nothing in either place, and no gateway, means there is no proxy to configure.
  2. Let the proxy or gateway pass the stream through. Anthropic's step is to configure any proxy or gateway between Claude Code and your model provider so it passes streaming response bodies and their headers through unmodified.
  3. On Amazon Bedrock, forward the body and the header. The response body and its Content-Type both have to arrive as Bedrock sent them. A gateway that rewrites the content-type is the case Anthropic warns about, and the common rewrite is text/event-stream.
  4. If the gateway only speaks the Messages API, connect it that way. Set ANTHROPIC_BASE_URL to the gateway and drop CLAUDE_CODE_USE_BEDROCK, as Anthropic describes for a gateway that re-emits Bedrock's stream as server-sent events.

If a proxy is in the path and it is not yours to change, the wider network checks are on Claude Code connection errors, including the curl test that separates a broken network from a broken hop.

How do I know it is fixed?

  • The warning stops appearing in a new interactive session, on turns that used to show it.
  • Replies start arriving incrementally as Claude writes, rather than the whole answer appearing only once it is complete. On a Bedrock gateway that drops the header and re-emits server-sent events, that slow path is the documented fallback symptom.
  • The warning does not come back in later sessions, once the hop between you and your model provider passes a whole stream again.

Where these answers come from

Common questions

Did I lose the reply?

No. Anthropic's entry says Claude Code re-sent the request without streaming to finish the turn, so the reply you see was produced by that second attempt.

Why was my request sent twice?

Because the streaming attempt delivered nothing usable. Anthropic documents that Claude Code sends each affected request twice: the empty streaming attempt and the retry.

Will I see this message on every turn?

No. Anthropic documents that Claude Code shows the warning once per session, and in interactive sessions only. It appears only when the streaming attempt comes back empty.

How do I tell whether I even have a proxy?

Check all four variables, not one. Anthropic documents that Claude Code takes the proxy from https_proxy, HTTPS_PROXY, http_proxy or HTTP_PROXY, using the first one that is set, and a value in a settings file's env block is read too. Run env | grep -i proxy, or Get-ChildItem Env:*proxy* in PowerShell, and check your settings file as well.

Is this my internet connection or the model provider?

Anthropic names a proxy or gateway between Claude Code and your model provider as the usual cause, because such a hop can consume or transform the streaming response body on its way back. With no proxy in the path there is no hop to fix, and the warning is only reporting the retry.

Do I need to update Claude Code?

Updating changes what you see rather than what happens. Before v2.1.239 Claude Code retried without streaming silently, so the retry itself is the same; the warning is the newer part.