Providers
OpenCode
OpenCode exposes two hosted catalogs in OpenClaw:
| Catalog | Prefix | Runtime provider |
|---|---|---|
| Zen | opencode/... |
opencode |
| Go | opencode-go/... |
opencode-go |
Both catalogs use the same OpenCode API key infrastructure (OPENCODE_API_KEY,
alias OPENCODE_ZEN_API_KEY). Go still requires its own paid subscription;
having a Zen key does not by itself grant Go access. OpenClaw keeps the runtime
provider ids split so upstream per-model routing stays correct.
Getting started
Zen catalog
Best for: the curated OpenCode multi-model proxy (Claude, GPT, Gemini, GLM, DeepSeek, Kimi, MiniMax, Qwen).
Run onboarding
openclaw onboard --auth-choice opencode-zenOr pass the key directly:
openclaw onboard --opencode-zen-api-key "$OPENCODE_API_KEY"Set a Zen model as the default
openclaw config set agents.defaults.model.primary "opencode/gpt-5.6-sol"Verify models are available
openclaw models list --provider opencodeGo catalog
Best for: the separately subscribed Go lineup across DeepSeek, GLM, GPT, Grok, Hy3, Kimi, MiMo, MiniMax, and Qwen.
Use the bundled Go catalog
OpenCode Go is included with OpenClaw for this release, so no separate plugin installation or Gateway restart is required.
Run onboarding
openclaw onboard --auth-choice opencode-goOr pass the key directly:
openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"Set a Go model as the default
openclaw config set agents.defaults.model.primary "opencode-go/kimi-k3"Verify models are available
openclaw models list --provider opencode-goConfig example
{ env: { vars: { OPENCODE_API_KEY: "sk-..." } }, agents: { defaults: { model: { primary: "opencode/gpt-5.6-sol" } } },}Provider catalogs
Zen
| Property | Value |
|---|---|
| Runtime provider | opencode |
| Example models | opencode/gpt-5.6-sol, opencode/kimi-k3, opencode/gemini-3.6-flash, opencode/minimax-m3, opencode/big-pickle |
Run openclaw models list --provider opencode for the current active list,
which also includes the promoted free-tier rows opencode/big-pickle,
opencode/deepseek-v4-flash-free, opencode/laguna-s-2.1-free,
opencode/ling-3.0-tiny-free, opencode/longcat-2.0-free,
opencode/mimo-v2.5-free,
opencode/nemotron-3-ultra-free, and opencode/north-mini-code-free.
Live discovery safely intersects OpenCode's returned IDs with trusted OpenClaw metadata. A key-scoped response can omit models that are unavailable to that workspace; that absence does not retire the offline definition. Deprecated explicit refs remain resolvable for existing configurations but are not shown as current recommendations.
Go
| Property | Value |
|---|---|
| Runtime provider | opencode-go |
| Example models | opencode-go/kimi-k3, opencode-go/gpt-5.6-luna, opencode-go/qwen3.8-max |
See OpenCode Go for the full Go model table.
Advanced configuration
API key aliases
OPENCODE_ZEN_API_KEY is also accepted as an alias for OPENCODE_API_KEY.
Shared credentials
Entering one OpenCode key during setup can store credentials for both runtime providers. It does not create a Go subscription or grant Go entitlement; subscribe to Go in the OpenCode console before using it.
Getting an API key
Create an OpenCode account and generate an API key at opencode.ai/auth. Billing and catalog availability are managed from the OpenCode dashboard.
Gemini replay behavior
Gemini-backed OpenCode refs stay on the proxy-Gemini path, so OpenClaw keeps Gemini thought-signature sanitation there without enabling native Gemini replay validation or bootstrap rewrites.
Non-Gemini replay behavior
Non-Gemini OpenCode refs keep the minimal OpenAI-compatible replay policy.
Pricing and privacy
Billing, retention, and training policies are model-specific. Check the current OpenCode Zen pricing and policy before selecting a route. Free models may be temporary feedback programs.
