OpenCode Go Catalog: Go Runtime Provider for OpenCode Setup
This page covers the OpenCode Go catalog, which uses the shared OpenCode setup and OPENCODE_API_KEY. It is intended for developers who need to route Go models through the opencode-go runtime provider.
Read this when
- You want the OpenCode Go catalog
- You need the runtime model refs for Go-hosted models
OpenCode Go functions as the Go catalog within OpenCode. While it uses the same OPENCODE_API_KEY credential as the Zen catalog, it maintains its own runtime provider identifier (opencode-go) to ensure proper per-model routing upstream.
| Property | Value |
|---|---|
| Runtime provider | opencode-go |
| Auth | OPENCODE_API_KEY (alias: OPENCODE_ZEN_API_KEY) |
| Parent setup | OpenCode |
Getting started
Interactive
Run onboarding
openclaw onboard --auth-choice opencode-go
Set a Go model as default
openclaw config set agents.defaults.model.primary "opencode-go/kimi-k2.6"
Verify models are available
openclaw models list --provider opencode-go
Non-interactive
Pass the key directly
openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
Verify models are available
openclaw models list --provider opencode-go
Config example
{
env: { OPENCODE_API_KEY: "YOUR_API_KEY_HERE" }, // pragma: allowlist secret
agents: { defaults: { model: { primary: "opencode-go/kimi-k2.6" } } },
}
Built-in catalog
Execute openclaw models list --provider opencode-go to see the current model list.
Included models:
| Model ref | Name | Context | Max output | Image input |
|---|---|---|---|---|
opencode-go/deepseek-v4-pro | DeepSeek V4 Pro | 1M | 384K | No |
opencode-go/deepseek-v4-flash | DeepSeek V4 Flash | 1M | 384K | No |
opencode-go/glm-5 | GLM-5 | 202,752 | 32,768 | No |
opencode-go/glm-5.1 | GLM-5.1 | 202,752 | 32,768 | No |
opencode-go/glm-5.2 | GLM-5.2 | 1M | 131,072 | No |
opencode-go/hy3-preview | HY3 Preview | 262,144 | 32,768 | No |
opencode-go/kimi-k2.5 | Kimi K2.5 | 262,144 | 65,536 | Yes |
opencode-go/kimi-k2.6 | Kimi K2.6 | 262,144 | 65,536 | Yes |
opencode-go/kimi-k2.7-code | Kimi K2.7 Code | 262,144 | 262,144 | Yes |
opencode-go/mimo-v2.5 | MiMo V2.5 | 1M | 128,000 | Yes |
opencode-go/mimo-v2.5-pro | MiMo V2.5 Pro | 1,048,576 | 128,000 | No |
opencode-go/minimax-m2.5 | MiniMax M2.5 | 204,800 | 65,536 | No |
opencode-go/minimax-m2.7 | MiniMax M2.7 | 204,800 | 131,072 | No |
opencode-go/minimax-m3 | MiniMax M3 | 204,800 | 131,072 | No |
opencode-go/qwen3.5-plus | Qwen3.5 Plus | 262,144 | 65,536 | Yes |
opencode-go/qwen3.6-plus | Qwen3.6 Plus | 262,144 | 65,536 | Yes |
opencode-go/qwen3.7-max | Qwen3.7 Max | 1M | 65,536 | No |
opencode-go/qwen3.7-plus | Qwen3.7 Plus | 1M | 65,536 | Yes |
Advanced configuration
Routing behavior
Any opencode-go/... model ref is automatically handled by OpenClaw routing. No additional provider configuration is needed.
Runtime ref convention
Runtime references are kept explicit: opencode/... points to Zen, opencode-go/... points to Go. This approach preserves correct per-model routing upstream for both catalogs.
Shared credentials
A single OPENCODE_API_KEY applies to both the Zen and Go catalogs. When you enter the key during setup, credentials are stored for both runtime providers.
Tip
Refer to OpenCode for the shared onboarding guide and the complete Zen plus Go catalog reference.
Related
-
OpenCode (parent), Shared onboarding, catalog overview, and advanced notes.
-
Model selection, Choosing providers, model refs, and failover behavior.