| Catalog | Prefix | Runtime provider |
|---|---|---|
| Zen | opencode/... | opencode |
| Go | opencode-go/... | opencode-go |
OPENCODE_API_KEY, alias
OPENCODE_ZEN_API_KEY). OpenClaw keeps the runtime provider ids split so
upstream per-model routing stays correct, but onboarding and docs treat them as
one OpenCode setup.
Getting started
- Zen catalog
- Go catalog
Config example
Built-in catalogs
Zen
| Property | Value |
|---|---|
| Runtime provider | opencode |
| Example models | opencode/claude-opus-4-6, opencode/gpt-5.5, opencode/gemini-3.1-pro, opencode/glm-5.2 |
openclaw models list --provider opencode for the full current list, which
also includes free-tier rows such as opencode/big-pickle and
opencode/deepseek-v4-flash-free.
Go
| Property | Value |
|---|---|
| Runtime provider | opencode-go |
| Example models | opencode-go/kimi-k2.6, opencode-go/glm-5, opencode-go/minimax-m2.5 |
Advanced configuration
API key aliases
API key aliases
OPENCODE_ZEN_API_KEY is also accepted as an alias for OPENCODE_API_KEY.Getting an API key
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 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 replay behavior
Non-Gemini OpenCode refs keep the minimal OpenAI-compatible replay policy.
Related
OpenCode Go
Full Go catalog reference.
Model selection
Choosing providers, model refs, and failover behavior.
Configuration reference
Full config reference for agents, models, and providers.