| summary: "Use the OpenCode Go catalog with the shared OpenCode setup" | |
| read_when: | |
| - You want the OpenCode Go catalog | |
| - You need the runtime model refs for Go-hosted models | |
| title: "OpenCode Go" | |
| # OpenCode Go | |
| OpenCode Go is the Go catalog within [OpenCode](/providers/opencode). | |
| It uses the same `OPENCODE_API_KEY` as the Zen catalog, but keeps the runtime | |
| provider id `opencode-go` so upstream per-model routing stays correct. | |
| ## Supported models | |
| - `opencode-go/kimi-k2.5` | |
| - `opencode-go/glm-5` | |
| - `opencode-go/minimax-m2.5` | |
| ## CLI setup | |
| ```bash | |
| openclaw onboard --auth-choice opencode-go | |
| # or non-interactive | |
| openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY" | |
| ``` | |
| ## Config snippet | |
| ```json5 | |
| { | |
| env: { OPENCODE_API_KEY: "YOUR_API_KEY_HERE" }, // pragma: allowlist secret | |
| agents: { defaults: { model: { primary: "opencode-go/kimi-k2.5" } } }, | |
| } | |
| ``` | |
| ## Routing behavior | |
| OpenClaw handles per-model routing automatically when the model ref uses `opencode-go/...`. | |
| ## Notes | |
| - Use [OpenCode](/providers/opencode) for the shared onboarding and catalog overview. | |
| - Runtime refs stay explicit: `opencode/...` for Zen, `opencode-go/...` for Go. | |