Cannot connect to API: The socket connection was closed unexpectedly

[kyler505]

Description

When using OpenCode, API connections intermittently fail with:

Cannot connect to API: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()

This error surfaces raw fetch() internals to the user rather than providing a meaningful error message or automatic recovery. While similar issues exist (#21643 for Zen models on QEMU, #22803 for SGLang ECONNRESET during streaming), this issue covers the general case where the underlying connection drops for any provider — including standard OpenAI/Anthropic endpoints on stable networks.

The core problem is that OpenCode does not gracefully handle transient socket closures. Expected behavior would be:

1. Automatic retry with backoff (not infinite loops like Streaming ECONNRESET / "socket connection was closed unexpectedly" with SGLang OpenAI-compatible provider during tool-using agent runs (Qwen3.5 + reasoning content) #22803)
2. A user-facing error message that explains the failure without exposing Bun/fetch internals
3. A way to configure timeout and retry behavior

Plugins

none

OpenCode version

1.4.6

Steps to reproduce

1. Use OpenCode with any provider (OpenAI, Anthropic, or custom OpenAI-compatible)
2. Run an extended session that involves multiple tool calls or streaming
3. Intermittently the socket drops and the raw error message appears

This is difficult to reproduce deterministically as it depends on network conditions, but occurs regularly in practice.

Screenshot and/or share link

No response

Operating System

Linux (various distributions)

Terminal

various

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used — please use one of the three required templates: Bug Report, Feature Request, or Question
• The Bug Report template requires a proper Description field, reproduction steps, and system information (OS, version, etc.)

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• Cannot connect to API: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch() #21643: Same error message — "Cannot connect to API: The socket connection was closed unexpectedly"
• Streaming ECONNRESET / "socket connection was closed unexpectedly" with SGLang OpenAI-compatible provider during tool-using agent runs (Qwen3.5 + reasoning content) #22803: Same "socket connection was closed unexpectedly" symptom during streaming with an OpenAI-compatible provider

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thank you for updating the issue! It now meets our contributing guidelines and includes all the required information. We appreciate you taking the time to provide the reproduction context, version, and system details.