Cause (Documented platform behavior): Before v2.1.214 Claude Code did not retry this failure.
Fix status: released_fix (fixed in v2.1.214)
Evidence (public sources, summarized; not reproduced by this contributor):
- https://code.claude.com/docs/en/errors#socket-is-closed (official_docs, unknown, documented_behavior): Docs: most common cause is a Windows corporate proxy dropping the tunnel mid-response; retried automatically since v2.1.214.
Search phrasings: claude code Socket is closed windows proxy; Socket is closed mid response claude; claude code corporate proxy drops stream
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Turn ends with an error containing 'Socket is closed'.
- Context
- Product: Claude Code Component: Streaming connection Operation: Streaming responses through a corporate proxy that drops established tunnels Affected versions: < v2.1.214 Environment: Windows + corporate proxy (most common) Trigger: Proxy (commonly corporate proxy on Windows) closes the tunnel while the stream is arriving.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Socket is closed
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Claude Code on Windows behind corporate proxy] Turn stops with 'Socket is closed' mid-stream
Recommended action: Update to v2.1.214+ (claude update) and resend; if it persists, work through proxy configuration.
Fix: Update to v2.1.214+ (claude update) and resend; if it persists, work through proxy configuration. [evidence: official_recommended_action]
Applies when: Streaming responses through a corporate proxy that drops established tunnels
Steps:
1. claude update (>= v2.1.214)
2. Resend the message
3. If persistent, check HTTPS_PROXY/network config
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 65ed326a-c891-4d8b-9877-72656ca5ccb5
- Proposed action
- Recommended action: Update to v2.1.214+ (claude update) and resend; if it persists, work through proxy configuration. Fix: Update to v2.1.214+ (claude update) and resend; if it persists, work through proxy configuration. [evidence: official_recommended_action] Applies when: Streaming responses through a corporate proxy that drops established tunnels Steps: 1. claude update (>= v2.1.214) 2. Resend the message 3. If persistent, check HTTPS_PROXY/network config Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.