[BUG] Claude Code transport issue
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Mid-turn, the Claude Code CLI aborted the streaming response with API Error: Stream idle timeout - partial response received. The assistant's turn was cut off before the tool call completed, and the session did not auto-resume — the user had to manually prompt the agent to continue.
What Should Happen?
Either (a) the CLI should recover transparently from a transient stream idle timeout without surfacing a partial response as a user-visible error, or (b) if the stream truly cannot recover, the CLI should automatically retry / resume the turn rather than leaving the session in a half-completed state that the user has to nudge back to life.
Steps to Reproduce
Run a long-running autonomous task in Claude Code (in this case, a Flutter-rewrite context-recovery session that reads many files in parallel and then begins authoring a mockup spec).
Let the assistant's turn include multiple parallel tool calls followed by a lengthy text generation.
Observe the stream stalling past the idle-timeout window, causing the CLI to emit the error and stop.
Error Messages/Logs
API Error: Stream idle timeout - partial response received
Steps to Reproduce
Run a long-running autonomous task in Claude Code (in this case, a Flutter-rewrite context-recovery session that reads many files in parallel and then begins authoring a mockup spec).
Let the assistant's turn include multiple parallel tool calls followed by a lengthy text generation.
Observe the stream stalling past the idle-timeout window, causing the CLI to emit the error and stop.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.0.123
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗