Skip to main content
OpenCode Go is a separate paid subscription inside OpenCode. It uses the same OPENCODE_API_KEY credential infrastructure as Zen, but a Zen key does not automatically include Go entitlement. Go keeps its own runtime provider id (opencode-go) so upstream per-model routing stays correct. OpenCode Go is bundled in the OpenClaw package for this release, so onboarding and configuration are sufficient; no separate plugin install is required.

​
Getting started

OpenCode Go is already included with OpenClaw for this release. Continue with interactive onboarding or pass the shared OpenCode API key directly.
1

Run onboarding

2

Set a Go model as default

3

Verify models are available

​
Config example

​
Catalog

Run openclaw models list --provider opencode-go for the current model list. Current active rows: Deprecated and preview refs remain resolvable only for existing explicit configurations. They are not part of static or live recommendations.

​
Privacy

OpenCode’s current policy says model training is not used for any active Go route. Grok 4.5 and GPT-5.6 Luna retain data for up to 30 days; the other active Go routes list zero-day retention. Review the current OpenCode Go privacy table before using a model, because provider policy can change independently of OpenClaw.

​
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.
The same OPENCODE_API_KEY can authenticate both runtime providers, so setup may store both profiles. Go access still requires a separate paid subscription in the OpenCode console.
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.