Volcano Engine setup (Doubao models, general + coding endpoints)
You want to use Volcano Engine or Doubao models with OpenClaw
You need the Volcengine API key setup
Volcengine (Doubao)
The Volcengine provider gives access to Doubao models and third-party models
hosted on Volcano Engine, with separate endpoints for general and coding
workloads.
Detail
Value
Providers
volcengine (general) + volcengine-plan (coding)
Auth
VOLCANO_ENGINE_API_KEY
API
OpenAI-compatible
Getting started
Run interactive onboarding:
```bash
openclaw onboard --auth-choice volcengine-api-key
```
This registers both the general (`volcengine`) and coding (`volcengine-plan`) providers from a single API key.
```json5
{
agents: {
defaults: {
model: { primary: "volcengine-plan/ark-code-latest" },
},
},
}
```
```bash
openclaw models list --provider volcengine
openclaw models list --provider volcengine-plan
```
For non-interactive setup (CI, scripting), pass the key directly:
`openclaw onboard --auth-choice volcengine-api-key` currently sets
`volcengine-plan/ark-code-latest` as the default model while also registering
the general `volcengine` catalog.
During onboarding/configure model selection, the Volcengine auth choice prefers
both `volcengine/*` and `volcengine-plan/*` rows. If those models are not
loaded yet, OpenClaw falls back to the unfiltered catalog instead of showing an
empty provider-scoped picker.
If the Gateway runs as a daemon (launchd/systemd), make sure
`VOLCANO_ENGINE_API_KEY` is available to that process (for example, in
`~/.openclaw/.env` or via `env.shellEnv`).
When running OpenClaw as a background service, environment variables set in your
interactive shell are not automatically inherited. See the daemon note above.
Related
Choosing providers, model refs, and failover behavior.
Full config reference for agents, models, and providers.
Common issues and debugging steps.
Frequently asked questions about OpenClaw setup.
