OpenCode Go

OpenCode Go

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.

Property	Value
Runtime provider	opencode-go
Auth	OPENCODE_API_KEY
Parent setup	OpenCode

Supported models

Model ref	Name
opencode-go/kimi-k2.5	Kimi K2.5
opencode-go/glm-5	GLM 5
opencode-go/minimax-m2.5	MiniMax M2.5

Getting started

Interactive

1. Run onboarding

   velaclaw onboard --auth-choice opencode-go
   
2. Set a Go model as default

   velaclaw config set agents.defaults.model.primary "opencode-go/kimi-k2.5"
   
3. Verify models are available

   velaclaw models list --provider opencode-go
   

Non-interactive

1. Pass the key directly

   velaclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
   
2. Verify models are available

   velaclaw 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.5" } } },
}

Advanced notes

Routing behavior

Velaclaw handles per-model routing automatically when the model ref uses opencode-go/.... No additional provider config is required.

Runtime ref convention

Runtime refs stay explicit: opencode/... for Zen, opencode-go/... for Go. This keeps upstream per-model routing correct across both catalogs.

Shared credentials

The same OPENCODE_API_KEY is used by 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.

Related

OpenCode (parent)

Shared onboarding, catalog overview, and advanced notes.

Model selection

Choosing providers, model refs, and failover behavior.