Skip to main content
OpenCode exposes two hosted catalogs in OpenClaw: 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

Best for: the curated OpenCode multi-model proxy (Claude, GPT, Gemini, GLM, DeepSeek, Kimi, MiniMax, Qwen).
1

Run onboarding

Or pass the key directly:
2

Set a Zen model as the default

3

Verify models are available

Config example

Provider catalogs

Zen

Run openclaw models list --provider opencode for the current active list. Model availability and promotional routes can change independently of OpenClaw. Live discovery combines the models available to your OpenCode account with authoritative model metadata from https://models.opencode.ai/api.json. OpenClaw fetches and caches that catalog only when OpenCode Zen or Go is configured or explicitly selected with OpenCode credentials; startup and unrelated providers never download it. New upstream models become available without an OpenClaw update when their metadata describes a supported transport on the trusted OpenCode endpoint. A key-scoped response can omit models unavailable to that workspace. Metadata and lifecycle status refresh together; deprecated models are excluded from active discovery and its offline fallback. Deprecated explicit refs remain resolvable for existing configurations but are not shown as current recommendations. Price estimates also refresh through the hosted model catalog, using the same public OpenCode pricing feed as live discovery. Hosted updates activate after the next Gateway restart; the bundled snapshot remains available offline. Explicit model prices in your configuration or agent-local models.json keep precedence. These are advertised-price estimates, not verified invoice totals.

Go

See OpenCode Go for discovery, routing, and access requirements. Go’s model-list endpoint advertises its general lineup; listing a model does not prove your account can run it.

Advanced configuration

OPENCODE_ZEN_API_KEY is also accepted as an alias for OPENCODE_API_KEY.
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.
Create an OpenCode account and generate an API key at opencode.ai/auth. Billing and catalog availability are managed from the OpenCode dashboard.
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 OpenCode refs keep the minimal OpenAI-compatible replay policy.
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.

OpenCode Go

Go catalog discovery and access requirements.

Model selection

Choosing providers, model refs, and failover behavior.

Configuration reference

Full config reference for agents, models, and providers.