Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt

Use this file to discover all available pages before exploring further.

OpenCode exposes two hosted catalogs in OpenClaw:
CatalogPrefixRuntime provider
Zenopencode/...opencode
Goopencode-go/...opencode-go
Both catalogs use the same OpenCode 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

Best for: the curated OpenCode multi-model proxy (Claude, GPT, Gemini).
1

Run onboarding

openclaw onboard --auth-choice opencode-zen
Or pass the key directly:
openclaw onboard --opencode-zen-api-key "$OPENCODE_API_KEY"
2

Set a Zen model as the default

openclaw config set agents.defaults.model.primary "opencode/claude-opus-4-6"
3

Verify models are available

openclaw models list --provider opencode

​
Config example

{
  env: { OPENCODE_API_KEY: "sk-..." },
  agents: { defaults: { model: { primary: "opencode/claude-opus-4-6" } } },
}

​
Built-in catalogs

​
Zen

PropertyValue
Runtime provideropencode
Example modelsopencode/claude-opus-4-6, opencode/gpt-5.5, opencode/gemini-3-pro

​
Go

PropertyValue
Runtime provideropencode-go
Example modelsopencode-go/kimi-k2.6, opencode-go/glm-5, opencode-go/minimax-m2.5

​
Advanced configuration

OPENCODE_ZEN_API_KEY is also supported as an alias for OPENCODE_API_KEY.
Entering one OpenCode key during setup stores credentials for both runtime providers. You do not need to onboard each catalog separately.
You sign in to OpenCode, add billing details, and copy your API key. 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.
Entering one OpenCode key during setup stores credentials for both the Zen and Go runtime providers, so you only need to onboard once.

Model selection

Choosing providers, model refs, and failover behavior.

Configuration reference

Full config reference for agents, models, and providers.