Repository navigation
Provider finish_reason: network_error with Ox Alpha Free (unlimited) #44379
Description
Description
Using the Ox Alpha Free (unlimited) model, OpenCode repeatedly returns Provider finish_reason: network_error during normal usage. The error appears inline in the chat as a red banner. The only workaround is opening a new chat session — the error persists within the same session.
This has been reported in #44358, #44360, and #44376 but those were auto-closed for not using the bug report template.
OpenCode version
latest (dev branch)
Steps to reproduce
- Configure OpenCode with the Ox Alpha Free (unlimited) model
- Start a chat session and send a few messages
- After several exchanges, the
network_errorfinish_reason appears - Continuing in the same session keeps producing the error
- Opening a new session temporarily fixes it until it recurs
Screenshot and/or share link
Error banner shows: Provider finish_reason: network_error
Operating System
macOS
Terminal
iTerm2
EDIT: Sorry for the duplicate issues. It was cause by network connectivity issues.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 23, 2026
This issue might be a duplicate of existing issues. Please check:
Provider finish_reason: network_errorwith Ox Alpha Free modelnetwork_errorfixed by opening a new sessiontoolsare included in requests, returningnetwork_erroror "Endpoint is unavailable"; plain chat without tools works fineThe underlying issue appears to be that the Ox Alpha Free model's tool-call path is unavailable/degraded on the Zen API. #44300 has the most detailed reproduction and analysis.
rugbedbugg commentedon Aug 24, 2026
Honestly, I think this is just a rate-limiting notification. It's really costly to give everyone unlimited access to a model.
wertsbework-stack commentedon Aug 24, 2026
I am experiencing the same issue with Ox Alpha Free (Unlimited), but I have an additional reproduction detail that may be useful.
Environment
Reproduction
The problem appears to be related to multiple concurrent OpenCode sessions.
Provider finish_reason: network_errorstarts occurring.The exact error is:
Provider finish_reason: network_errorThis makes me suspect that the issue may involve provider capacity, concurrency, connection handling, rate limiting, or a recent backend change.
The important detail is that 5 concurrent sessions worked normally yesterday, while today the same setup starts failing above approximately 3 concurrent sessions.
I am using the OpenCode Desktop App, not a terminal-based OpenCode client.
I am adding this information here because this appears to be the same Ox Alpha Free (Unlimited)
network_errorissue.rugbedbugg commentedon Aug 24, 2026
For me I have only ever used 2 sessions (max 3) at once, and the error still occurs. The peculiar thing in my case is that if the issue resolves itself, it will only start working for new sessions at first. Already started sessions take longer to recover.
DSCmatter commentedon Aug 24, 2026
@rugbedbugg @wertsbework-stack I'm getting the same error: "Provider finish_reason: network_error"
cant even use any model not just 0x Alpha but even Big pickle
rekram1-node commentedon Aug 24, 2026
We are working with the provider of the stealth model, but they are having issues on their end, not too much we can do until it gets resolved. We do automatically retry these errors in opencode but if they happen for extended period of time, the session will come to a halt.
neriousy commentedon Oct 20, 2026
A maintainer confirmed that Ox Alpha's provider was experiencing failures on its side, rather than in OpenCode. Closing this as an upstream provider issue; please contact the model provider's maintainers if it continues.