openclaw/docs/providers/opencode-go.md at e8a162d3d8a0643416098f612108c3546efd8733

mirror of https://github.com/openclaw/openclaw.git synced 2026-03-12 07:20:45 +00:00

Files

Luke 7761e7626f Providers: add Opencode Go support (#42313 )

* feat(providers): add opencode-go provider support and onboarding

* Onboard: unify OpenCode auth handling openclaw#42313 thanks @ImLukeF

* Docs: merge OpenCode Zen and Go docs openclaw#42313 thanks @ImLukeF

* Update CHANGELOG.md

---------

Co-authored-by: Ubuntu <ubuntu@vps-90352893.vps.ovh.ca>
Co-authored-by: Vincent Koc <vincentkoc@ieee.org>

2026-03-11 01:31:06 -04:00

1.1 KiB

Raw Blame History

summary, read_when, title

summary

read_when

title

Use the OpenCode Go catalog with the shared OpenCode setup

You want the OpenCode Go catalog

You need the runtime model refs for Go-hosted models

OpenCode Go

OpenCode Go is the Go catalog within OpenCode. It uses the same OPENCODE_API_KEY as the Zen catalog, but keeps the runtime provider id opencode-go so upstream per-model routing stays correct.

Supported models

opencode-go/kimi-k2.5
opencode-go/glm-5
opencode-go/minimax-m2.5

CLI setup

openclaw onboard --auth-choice opencode-go
# or non-interactive
openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"

Config snippet

{
  env: { OPENCODE_API_KEY: "YOUR_API_KEY_HERE" }, // pragma: allowlist secret
  agents: { defaults: { model: { primary: "opencode-go/kimi-k2.5" } } },
}

Routing behavior

OpenClaw handles per-model routing automatically when the model ref uses opencode-go/....

Notes

Use OpenCode for the shared onboarding and catalog overview.
Runtime refs stay explicit: opencode/... for Zen, opencode-go/... for Go.

1.1 KiB Raw Blame History