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.

PropertyValue
Runtime provideropencode-go
AuthOPENCODE_API_KEY (alias: OPENCODE_ZEN_API_KEY)
Parent setupOpenCode

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 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.5MiMo V2.51M128,000Yes
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

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.