Skip to main content
OpenCode exposes two hosted catalogs in FluffBuzz: Both catalogs use the same OpenCode API key. FluffBuzz 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

Or pass the key directly:
2

Set a Zen model as the default

3

Verify models are available

​
Config example

​
Built-in catalogs

​
Zen

​
Go

​
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 FluffBuzz 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.