Skip to main content
OpenCode Go is the Go catalog inside OpenCode. It shares the OPENCODE_API_KEY credential with the Zen catalog, but keeps its own runtime provider id (opencode-go) so upstream per-model routing stays correct.
PropertyValue
Runtime provideropencode-go
AuthOPENCODE_API_KEY (alias: OPENCODE_ZEN_API_KEY)
Parent setupOpenCode

​
Getting started

1

Run onboarding

openclaw onboard --auth-choice opencode-go
2

Set a Go model as default

openclaw config set agents.defaults.model.primary "opencode-go/kimi-k2.6"
3

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

Run openclaw models list --provider opencode-go for the current model list. Bundled rows:
Model refNameContextMax outputImage input
opencode-go/deepseek-v4-proDeepSeek V4 Pro1M384KNo
opencode-go/deepseek-v4-flashDeepSeek V4 Flash1M384KNo
opencode-go/glm-5GLM-5202,75232,768No
opencode-go/glm-5.1GLM-5.1202,75232,768No
opencode-go/glm-5.2GLM-5.21M131,072No
opencode-go/hy3-previewHY3 Preview262,14432,768No
opencode-go/kimi-k2.5Kimi K2.5262,14465,536Yes
opencode-go/kimi-k2.6Kimi K2.6262,14465,536Yes
opencode-go/kimi-k2.7-codeKimi K2.7 Code262,144262,144Yes
opencode-go/mimo-v2-omniMiMo V2 Omni262,14432,000Yes
opencode-go/mimo-v2.5MiMo V2.51M128,000Yes
opencode-go/mimo-v2-proMiMo V2 Pro1,048,57632,000No
opencode-go/mimo-v2.5-proMiMo V2.5 Pro1,048,576128,000No
opencode-go/minimax-m2.5MiniMax M2.5204,80065,536No
opencode-go/minimax-m2.7MiniMax M2.7204,800131,072No
opencode-go/minimax-m3MiniMax M3204,800131,072No
opencode-go/qwen3.5-plusQwen3.5 Plus262,14465,536Yes
opencode-go/qwen3.6-plusQwen3.6 Plus262,14465,536Yes
opencode-go/qwen3.7-maxQwen3.7 Max1M65,536No
opencode-go/qwen3.7-plusQwen3.7 Plus1M65,536Yes

​
Advanced configuration

OpenClaw routes any opencode-go/... model ref automatically. No extra provider config is required.
Runtime refs stay explicit: opencode/... for Zen, opencode-go/... for Go. This keeps upstream per-model routing correct across both catalogs.
One OPENCODE_API_KEY covers both the Zen and Go catalogs. Entering the key during setup stores credentials for both runtime providers.
See OpenCode for the shared onboarding overview and the full Zen + Go catalog reference.

OpenCode (parent)

Shared onboarding, catalog overview, and advanced notes.

Model selection

Choosing providers, model refs, and failover behavior.