OpenCode Go - OpenClaw
OpenClawDocs
View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page

Providers

OpenCode Go

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, so onboarding and configuration are sufficient; no separate plugin install is required.

Property Value
Runtime provider opencode-go
Plugin Bundled (opencode-go)
Auth OPENCODE_API_KEY (alias: OPENCODE_ZEN_API_KEY)
Parent setup OpenCode

Getting started

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

Interactive

  • Run onboarding

    bash
    openclaw onboard --auth-choice opencode-go

  • Set a Go model as default

    bash
    openclaw config set agents.defaults.model.primary "opencode-go/kimi-k3"

  • Verify models are available

    bash
    openclaw models list --provider opencode-go

    • Non-interactive

  • Pass the key directly

    bash
    openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"

  • Verify models are available

    bash
    openclaw models list --provider opencode-go

    • Config example

    json5
    {  env: { vars: { OPENCODE_API_KEY: "YOUR_API_KEY_HERE" } }, // pragma: allowlist secret  agents: { defaults: { model: { primary: "opencode-go/kimi-k3" } } },}

    Catalog

    Run openclaw models list --provider opencode-go for the current model list. OpenClaw combines Go's advertised model IDs with authoritative metadata from https://models.opencode.ai/api.json, so new upstream models appear without an OpenClaw update when they use a supported transport on the trusted OpenCode endpoint. The upstream catalog is downloaded and cached only when OpenCode Zen or Go is configured or explicitly selected with OpenCode credentials; it is never fetched at startup or while using unrelated providers.

    Example refs include opencode-go/deepseek-v4-flash, opencode-go/kimi-k3, and opencode-go/qwen3.8-max. Use the CLI for the current lineup rather than treating these examples as an inventory. OpenClaw excludes deprecated rows from active discovery and applies refreshed lifecycle status to its offline fallback. Bundled preview rows stay hidden until accepted upstream metadata supplies them. Existing explicit refs in the bundled seed remain resolvable.

    The Go model-list endpoint is a general inventory, not an account-entitlement check. A successful listing does not grant access: inference still requires an active Go subscription, including for promotional models.

    Privacy

    Retention and training policies vary by model. Review the current OpenCode Go privacy table before using a model, because provider policy can change independently of OpenClaw.

    Advanced configuration

    Routing behavior

    OpenClaw routes any opencode-go/... model ref automatically. No extra provider config is required.

    Runtime ref convention

    Runtime refs stay explicit: opencode/... for Zen, opencode-go/... for Go. This keeps upstream per-model routing correct across both catalogs.

    Shared credentials

    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.

    OpenCode (parent)

    Shared onboarding, catalog overview, and advanced notes.
    Model selection

    Choosing providers, model refs, and failover behavior.
    Was this useful?
    On this page

    On this page