You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenCode Go: union-alpha fails with 503 'Upstream request failed: Endpoint is unavailable' on tool calls #49413
When using opencode-go/union-alpha, plain prompt requests (without tools) work as expected, but any turn that involves tool calling (e.g. read, write, bash) consistently triggers a 503 Service Unavailable from the provider gateway:
{"type":"error","error":{"type":"api_error","message":"Error from provider (Console Go): Upstream request failed: Endpoint is unavailable."}}
Steps to Reproduce
Tested on OpenCode 1.18.31 (and third-party agents like Pi):
This issue tracks the currently active catalog model opencode-go/union-alpha on OpenCode v1.18.31, where the exact same tool-calling adapter degradation persists on the Go route (https://opencode.ai/zen/go/v1/messages).
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.
Activity
github-actions commentedon Sep 16, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct (e.g. specifically affects
union-alphawith tool calls in a way not covered by the above), please add clarifying details.herbertnikolajewskidci commentedon Sep 16, 2026
Clarification regarding the bot flags:
x-preview-f-free/ox-alpha-free) and is already closed.opencode-go/union-alphaon OpenCode v1.18.31, where the exact same tool-calling adapter degradation persists on the Go route (https://opencode.ai/zen/go/v1/messages).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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊