openclaw - 💡(How to fix) Fix opencode-go plugin: missing models in static catalog (Qwen3.6 Plus, MiMo-V2.5-Pro, Kimi-K2.6) [2 comments, 3 participants]

Problem

The opencode-go plugin in OpenClaw uses a static model catalog that only includes 3 models:

• opencode-go/kimi-k2.5
• opencode-go/glm-5
• opencode-go/minimax-m2.5

However, the OpenCode Go API (endpoint: https://opencode.ai/zen/go/v1/chat/completions) supports many more models, including:

• qwen3.6-plus
• qwen3.5-plus
• mimo-v2.5-pro
• mimo-v2.5
• mimo-v2-pro
• mimo-v2-omni
• kimi-k2.6

When these models are configured as fallbacks (e.g. opencode-go/Qwen3.6 Plus), OpenClaw returns model_not_found without ever calling the API, and falls back to the next model in the chain.

Evidence

1. Direct API call to https://opencode.ai/zen/go/v1/chat/completions with model qwen3.6-plus succeeds with HTTP 200 and valid response.

2. openclaw models list --provider opencode-go shows new models as missing:

opencode-go/MiMo-V2.5-Pro - - - - missing
opencode-go/Qwen3.6 Plus   - - - - missing
opencode-go/Kimi-K2.6      - - - - missing

1. Working models (in catalog):

opencode-go/kimi-k2.5    text+image 256k no yes fallback#1
opencode-go/glm-5        text 200k no yes fallback#2
opencode-go/minimax-m2.5 text 200k no yes fallback#3

Expected behavior

Models supported by the OpenCode Go API should be registered in the plugin's static catalog so OpenClaw can resolve them without calling the API first (avoiding unnecessary failover delay).

Environment

• OpenClaw: 2026.4.21
• Plugin: opencode-go (bundled, stock)
• API key: OPENCODE_API_KEY configured

Suggested fix

Update the static catalog in dist/onboard-Bydjn1C5.js (or the source equivalent) to include the full list of OpenCode Go models currently supported by the API.

Reference: https://opencode.ai/docs/go/