Models / Providers

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.

Built-in catalog

Genesis sources the Go catalog from the bundled pi model registry. Run genesis models list --provider opencode-go for the current model list.

As of the bundled pi catalog, the provider includes:

Getting started

Interactive

Run onboarding

genesis onboard --auth-choice opencode-go

Set a Go model as default

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

Verify models are available

genesis models list --provider opencode-go

Non-interactive

Pass the key directly

genesis onboard --opencode-go-api-key "$OPENCODE_API_KEY"

Verify models are available

genesis 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" } } },
}

Advanced configuration

Routing behavior

Genesis 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.

Related

• OpenCode (parent) Shared onboarding, catalog overview, and advanced notes.

• Model selection Choosing providers, model refs, and failover behavior.