openclaw - 💡(How to fix) Fix Bundled opencode-go plugin hits /go/v1 (404 HTML) instead of /zen/go/v1 [1 comments, 2 participants]

Summary

After upgrading to 2026.4.20, every model served by the bundled opencode-go plugin fails with:

FailoverError: The provider returned an HTML error page instead of an API response. This usually means a CDN or gateway (e.g. Cloudflare) blocked the request.

The plugin appears to be hitting https://opencode.ai/go/v1/... (404 HTML) instead of the correct https://opencode.ai/zen/go/v1/.... A custom provider pointed at https://opencode.ai/zen/go/v1 with the same OPENCODE_API_KEY works fine, which isolates the problem to the bundled plugin's baseUrl.

Environment

• OpenClaw 2026.4.20 (build 115f05d), installed via npm -g
• Node v22.22.2, Linux 6.8.0-106-generic
• Gateway mode local, systemd unit

Reproduction

With a clean opencode-go plugin entry enabled and any bundled model (e.g. opencode-go/kimi-k2.5, opencode-go/minimax-m2.7, opencode-go/mimo-v2-omni), invoke:

openclaw infer model run --model opencode-go/kimi-k2.5 \
  --prompt 'reply with PONG'

Result: FallbackSummaryError: All models failed (...): model_not_found with "The provider returned an HTML error page ...". Fallback to opencode-go/mimo-v2-pro fails identically.

Evidence the URL path is wrong

Direct probes with a bogus bearer to rule out auth vs path:

$ curl -sS -o /dev/null -w '%{http_code} %{content_type}\n' \
    -X POST https://opencode.ai/go/v1/chat/completions \
    -H 'Authorization: Bearer nope' -H 'Content-Type: application/json' \
    -d '{"model":"kimi-k2.5","messages":[{"role":"user","content":"ping"}]}'
404 text/html

$ curl -sS -o /dev/null -w '%{http_code} %{content_type}\n' \
    -X POST https://opencode.ai/zen/go/v1/chat/completions \
    -H 'Authorization: Bearer nope' -H 'Content-Type: application/json' \
    -d '{"model":"kimi-k2.5","messages":[{"role":"user","content":"ping"}]}'
401 text/plain;charset=UTF-8

The /go/v1 path returns a 404 HTML page. The /zen/go/v1 path returns a 401 plaintext — endpoint exists, just rejecting the bad token. The error surfaced in OpenClaw ("HTML error page") matches the first case exactly.

Workaround

Bundled plugin's config schema has empty properties: {} so no baseUrl override is exposed. Working workaround is a custom provider:

\"custom-opencode-go-extras\": {
  \"baseUrl\": \"https://opencode.ai/zen/go/v1\",
  \"api\": \"openai-completions\",
  \"apiKey\": { \"source\": \"env\", \"provider\": \"default\", \"id\": \"OPENCODE_API_KEY\" },
  \"models\": [ { \"id\": \"kimi-k2.5\", ... }, ... ]
}

All 5 of our agents route cleanly through that — same API key, same host, different path — which further confirms /zen/go/v1 is the intended base.

Expected

Bundled opencode-go plugin should hit https://opencode.ai/zen/go/v1 (or expose baseUrl as an overridable config field).

Notes

Not a regression in 2026.4.15 (our prior version) — bundled opencode-go/* routes worked there.