ImageOpenClawDocs
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 for this release, 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 for this release. 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. Current active rows:

    Model ref Context Max output Inputs Transport
    opencode-go/deepseek-v4-flash 1M 384K Text Chat
    opencode-go/deepseek-v4-pro 1M 384K Text Chat
    opencode-go/glm-5.1 202,752 32,768 Text Chat
    opencode-go/glm-5.2 1M 131,072 Text Chat
    opencode-go/gpt-5.6-luna 1.05M 128,000 Text, image Responses
    opencode-go/grok-4.5 500,000 500,000 Text, image Chat
    opencode-go/hy3 256,000 64,000 Text Chat
    opencode-go/kimi-k2.6 262,144 65,536 Text, image Chat
    opencode-go/kimi-k2.7-code 262,144 262,144 Text, image Chat
    opencode-go/kimi-k3 1,048,576 131,072 Text, image Chat
    opencode-go/mimo-v2.5 1M 128,000 Text, image Chat
    opencode-go/mimo-v2.5-pro 1,048,576 128,000 Text Chat
    opencode-go/minimax-m2.7 204,800 131,072 Text Messages
    opencode-go/minimax-m3 1M 131,072 Text, image Messages
    opencode-go/qwen3.6-plus 1M 65,536 Text, image Messages
    opencode-go/qwen3.7-max 1M 65,536 Text Messages
    opencode-go/qwen3.7-plus 1M 65,536 Text, image Messages
    opencode-go/qwen3.8-max 1M 131,072 Text, image Messages

    Deprecated and preview refs remain resolvable only for existing explicit configurations. They are not part of static or live recommendations.

    Privacy

    OpenCode's current policy says model training is not used for any active Go route. Grok 4.5 and GPT-5.6 Luna retain data for up to 30 days; the other active Go routes list zero-day retention. 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