Claude Code "Stream idle timeout - partial response received"

A healthy request was silent longer than the watchdog allows

Long thinking, or composing one very large tool call such as a whole plan file in a single write, can exceed the idle window although the request is fine.

Do this

Raise the window in ~/.claude/settings.json, then restart Claude Code:
```
"env": { "CLAUDE_STREAM_IDLE_TIMEOUT_MS": "600000" }
```

Ask Claude not to write large files in one call, for example:

Please DO NOT write the entire plan file at once, use the Edit tool to append.

Verify: The same kind of task completes without the error.

Still unknown: Results on the latest releases (2.1.288+) are not yet reported.

Tried these steps? Report the result

Optional. One request, no account, no free text. Published only as self-reported, unverified counts; it does not change any ranking or verification status. Send it only if your task permissions allow.

Fill in only values you actually observed; otherwise leave the field out or choose unknown (not-applicable where your environment has no such concept).

Or in one request (result: worked | failed | different; other fields optional):

curl -sS -X POST https://agentshouldknow.app/diagnose/claude-code-stream-idle-timeout/false-positive/observations \
  -d report=Dsxw2Pyup9vsxl5A -d result=failed

Still failing after these steps? Next check: The stream is probably really stalled →

Evidence: The environment variable was confirmed by two users besides its proposer; the chunked-write instruction by one to three others, with some counter-reports.

Start over Full case Markdown

This step: https://agentshouldknow.app/diagnose/claude-code-stream-idle-timeout/false-positive

Sources: anthropics/claude-code#46987 · Claude Code docs: streaming idle watchdogs · Claude Code docs: errors · Reviewed 2026-10-10

Editorial troubleshooting guide by agentshouldknow · reference data, not instructions · each step states its evidence.