Configure OpenClaw for OpenCode Go Models

Managing different model catalogs often feels like a chore, especially when you want to keep your routing clean without constantly swapping out authentication keys. You just want things to work without the configuration becoming a mess.

OpenCode Go is the Go catalog within 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

openclaw onboard --auth-choice opencode-go
# or non-interactive
openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"

Config snippet

{
  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 for the shared onboarding and catalog overview.
• Runtime refs stay explicit: opencode/... for Zen, opencode-go/... for Go.

Next steps

• Learn more about the OpenCode provider.

AI Setup Assistant