Repository navigation
Title Ox Alpha Free fails with "Endpoint is unavailable" when OpenCode uses tools #44850
Description
I am using OpenCode with the Ox Alpha Free model.
The model works for normal conversation, but when OpenCode tries to use a tool, the request fails with:
Error from provider (Console): Upstream request failed:
Endpoint is unavailable.
This happened while OpenCode was working on an NVGT project and attempted to execute a shell command:
& "C:\nvgt\nvgt.exe" -c server.nvgt 2>&1 | Select-Object
The problem is not an NVGT error. OpenCode does not receive the tool result because the Ox Alpha provider request itself fails with "Endpoint is unavailable."
Steps to reproduce
1.
Open OpenCode.
2.
Select Ox Alpha Free.
3.
Open a coding project.
4.
Ask the model to perform a task that requires a tool, such as running a shell command.
5.
Allow OpenCode to execute the tool.
6.
The request fails with Endpoint is unavailable.
Actual behavior
The tool call fails and OpenCode reports:
Error from provider (Console): Upstream request failed:
Endpoint is unavailable.
The model cannot receive the command output and therefore cannot continue the task.
Expected behavior
Ox Alpha Free should successfully handle the tool call and return the tool result to OpenCode so the model can continue working.
Additional information
This appears to happen specifically when Ox Alpha Free is used through OpenCode and a tool call is involved.
Normal model interaction can work, but tool execution fails with the upstream endpoint error.
I have retried the request, but the same error occurs.
Environment
•
OS: Windows 11
•
Client: OpenCode
•
Model: Ox Alpha Free
•
Tool: Shell / command execution
•
Project: NVGT game development
Error
Upstream request failed: Endpoint is unavailable.
Activity
github-actions commentedon Aug 25, 2026
This issue might be a duplicate of existing issues. Please check:
These issues describe the same symptom: ox-alpha-free (and related free models) returning an upstream "Endpoint is unavailable" error specifically when a tool call is involved. Your report appears to be the same underlying issue.
EmranHejazi commentedon Aug 25, 2026
I just faced the same issue, and simply I just went to a new session and tested the model, and the model was responding perfectly. The issue was the context window. I think they're limiting the context window, and I reached around 45%, and this happened.
muazazhar commentedon Aug 25, 2026
I'm facing the same issue. my context is at 34% and i'm receiving this error even in new session
Hochgeschwindigkeitsrennfahrer commentedon Aug 25, 2026
Same here
EmranHejazi commentedon Aug 25, 2026
try to compact the session with another model, and after compaction, you'll be able to use the Ox model inside that session again.
ronitchhabria commentedon Aug 25, 2026
The issue is images right now if u send even 1x1 px image it throws the error
GhostMan612 commentedon Aug 25, 2026
just /compact the session then copy/paste the response into new session. if you're using SESSION_HANDOFF.md and ROADMAP.md and CURRENT_STATE.md files, be sure to update those as well before starting new session. my projects all work after doing just that
muazazhar commentedon Aug 26, 2026
I tried this. it started working but in same response after 3,4 seconds it gave same error
muazazhar commentedon Aug 26, 2026
giving error without images too
GhostMan612 commentedon Aug 27, 2026
It was probably your image size, not in pixels but in actual storage size. I ran into same issue with assets and just backed off after awhile. Reset and restarted opencode with a fresh session and did a cold start. Like you said, it ran for a little bit then I had to restart a new session with a fresh cold start. Are you using blueprints and a documentation set to keep track of your progress?
Your context window can easily be used by agents who are reading ten to twenty files while testing pipelines so maybe you have a dead loop somewhere in your code. I has that issue yesterday where nemotron was running a dart test for HOURS before finally realizing that the flutter tests I had in place were already functional so it reverted back to those instead. Now I'm running back a lot full capacity. Just no Ox Alpha Free Unlimited, which is fine. I got most of my research & planning done during the free preview and now I just have a bunch of specs and blueprints to follow using lesser models. No issues as of yet..
Tarquinen commentedon Oct 20, 2026
Thanks for the report! Ox Alpha is no longer offered on Zen or Go, so this no longer applies. Closing this issue.
— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊