anomalyco / anomalyco/opencode
[Zen Go] ox-alpha-free /v1/responses still 500 on 2026-08-26 despite merged responses-adapter fixes — Codex (Go plan) remains fully down
@fwang is already working on this.
Since Aug 26, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Summary
Since ~2026-08-23, ox-alpha-free on the Zen Go endpoint (https://opencode.ai/zen/go/v1) returns HTTP 500 on every /v1/responses request \u2014 regardless of streaming or tools. The same model succeeds on all four /v1/chat/completions variants. This is a deterministic 100% outage for clients speaking only the Responses wire protocol (OpenAI Codex CLI/Desktop) on the Go subscription.
This corroborates #44910 with fresh 2026-08-26 data: the failure persists after yesterday's merged adapter fixes (#45013, #45050, #45081, #45085).
Environment
- Endpoint:
https://opencode.ai/zen/go/v1(Go subscription) - Client: Codex CLI 0.147.0 (
wire_api = "responses"), Windows 11 - Probes fired directly at opencode.ai (local proxy bypassed; browser UA to avoid CF 403)
- Two independent Go-subscription keys produced identical split behavior on 08-25 \u2192 rules out account-level rate limiting (also: no 429 anywhere, instant 500)
Probe matrix \u2014 2026-08-26 00:25 UTC (ox-alpha-free)
| endpoint | stream | tools | result |
|---|---|---|---|
| chat/completions | false | false | 200 OK (2.8s) |
| chat/completions | false | true | 200 OK (7.3s) |
| chat/completions | true | false | 200 OK (1.9s) |
| chat/completions | true | true | 200 OK (5.5s) |
| responses | false | false | 500 FAIL (<1s) {"type":"error","error":{"type":"error","message":"Internal server error"}} |
| responses | false | true | 500 FAIL (<1s) same |
| responses | true | false | 500 FAIL (<1s) same |
| responses | true | true | 500 FAIL (<1s) same |
Control deepseek-v4-flash: all 8 cells \u2192 200 OK.
Client-side symptom
Codex retries 5 times then surfaces "We're currently experiencing high demand" \u2014 misleading, since upstream answers with an instant 500 (<1s), not a load-shedding response.
Timeline
- 08-23: tools-bearing requests begin failing (#44300, #44382)
- 08-24: transient recovery noted in #44503, regressed afterwards
- 08-25 ~13:00 UTC+8: entire
/v1/responsespath down for non-DeepSeek models (#44910 \u2014 its evidence matrix matches mine cell-for-cell) - 08-25 15:50\u201322:14 UTC: responses-adapter fixes merged: #45013, #45050, #45081, #45085 (#45038, #45094 still open)
- 08-26 00:25 UTC: probe unchanged \u2014 responses still 4/4 cells 500
Minimal repro
# -> 500 in <1s
curl -s https://opencode.ai/zen/go/v1/responses \
-H "Authorization: Bearer $GO_KEY" -H "Content-Type: application/json" \
-d '{"model":"ox-alpha-free","input":[{"role":"user","content":[{"type":"input_text","text":"reply ok"}]}]}'
# -> 200 OK
curl -s https://opencode.ai/zen/go/v1/chat/completions \
-H "Authorization: Bearer $GO_KEY" -H "Content-Type: application/json" \
-d '{"model":"ox-alpha-free","messages":[{"role":"user","content":"reply ok"}]}'
Ask
The merged responses-adapter fixes (#45013/#45050/#45081/#45085) don't appear to have reached the Zen Go gateway yet. Could you confirm whether they're pending deployment to the go/v1 route, or whether this needs a separate fix? Happy to re-run the full probe matrix once deployed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.