Repository navigation
Description
Description
Hello OpenCode Team,
I am experiencing a recurring connectivity problem in OpenCode Desktop on Windows.
The error is:
Cannot connect to API: Connect Timeout Error
(attempted addresses: 172.65.90.21:443,
2606:4700:78::90:0:142:443,
172.65.90.23:443,
2606:4700:78::90:0:140:443,
172.65.90.20:443,
2606:4700:78::90:0:141:443,
172.65.90.22:443,
2606:4700:78::90:0:143:443,
timeout: 10000ms)
This is reproducible and is not limited to a single model. The OpenCode log shows the same failure with multiple models, including:
muse-spark-1.2-contributor-free
muse-spark-1.3-contributor-free
mimo-v2.5-free
The failures occur repeatedly across September 11–13, 2026.
Local network tests
I tested the same machine outside OpenCode:
TCP connectivity:
Test-NetConnection 172.65.90.22 -Port 443
TcpTestSucceeded : True
HTTPS to OpenCode:
curl.exe -I -v --connect-timeout 10 https://opencode.ai/
Result:
HTTP/1.1 200 OK
HTTPS to Models.dev:
curl.exe -I -v --connect-timeout 10 https://models.dev/
Result:
HTTP/1.1 200 OK
Therefore, direct HTTPS connectivity from the Windows machine to both opencode.ai and models.dev works successfully.
OpenCode-specific behavior
However, OpenCode Desktop repeatedly logs:
Failed to fetch models.dev
cause=TimeoutError
and:
Cannot connect to API: Connect Timeout Error
timeout: 10000ms
The log also contains an earlier DNS error:
Cannot connect to API: getaddrinfo ENOTFOUND opencode.ai
although DNS resolution currently works from Windows.
I also tested PowerShell separately. Interestingly, curl.exe can reach models.dev and receives HTTP 200, while Invoke-WebRequest has at times reported:
The remote name could not be resolved: 'models.dev'
This suggests there may be a difference between the network/runtime stack used by OpenCode Desktop and the normal Windows command-line networking tools.
Additional log information
The OpenCode log also contains:
background dependency install failed
ReleaseError: token mismatch
which may indicate a cache/dependency problem, although I cannot confirm that this is the root cause.
The application version recorded in the log is:
1.18.30
Current environment
Windows
OpenCode Desktop
OpenCode Desktop version: 1.18.30
No HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, or OPENCODE_* environment variables were found in PowerShell.
No API key or bearer token is included in the attached log excerpts.
Request
Could you please investigate whether this is a known Windows/OpenCode Desktop networking issue involving the Desktop runtime, Bun/Node/Undici networking, DNS resolution, IPv4/IPv6 handling, or models.dev connectivity?
In particular, I would appreciate clarification on why:
Windows curl → opencode.ai 200 OK
Windows curl → models.dev 200 OK
OpenCode Desktop → models.dev Timeout
OpenCode Desktop → API Connect Timeout
Please let me know whether there is a known fix, workaround, or diagnostic build for this issue.
I can provide the relevant sanitized log excerpts and additional diagnostic results if needed.
Thank you.
Best regards,
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
Windows11
Terminal
powershell
Activity
github-actions commentedon Sep 13, 2026
This issue might be a duplicate of existing issues. Please check:
Cannot connect to API+AggregateErroron high-latency providers (z.ai/GLM, DashScope/Qwen) — Node’s 250 ms connect-attempt cap; same provider works in the CLI #45178:Cannot connect to API+AggregateErrorin Desktop on high-latency providers — the same error message and the same root cause (Desktop runs on Electron/Node with undici, which applies a 250 ms Happy Eyeballs connect-attempt cap; Bun-based CLI on the same machine is unaffected). That issue also documents a workaround and a suggested fix.models.devfetch on Windows — covers theFailed to fetch models.dev/TimeoutErrorsymptom you're seeing, including under packet-drop conditions.thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊