Kling 4.0 is LIVE — Unbelievably Real Video | Try Now →
Agent Setup

Connect Continue CLI to WaveSpeed LLM API

Copy the recommended ~/.continue/config.yaml setup for Continue CLI, route requests to /v1/chat/completions, and verify local agent calls in WaveSpeed Logs.

Continue's CLI agent; add WaveSpeed as an OpenAI-compatible model.

Config file

~/.continue/config.yaml

Protocol

OpenAI-compatible chat completions

Endpoint

/v1/chat/completions

Manual setup

1

Create a WaveSpeed access key

2

Export the required key locally

3

Paste config into~/.continue/config.yaml

4

Run cn and check Logs

OpenAI-compatible chat completions

Usage appears in Dashboard and Logs

Switch models without rewriting agent code

One-command setup

Configures Continue CLI, checks that it works, and backs up your previous settings. Add --undo to restore them.

  1. 1

    Install the WaveSpeed CLI

    npm install -g @wavespeed/cli
  2. 2

    Sign in

    wavespeed login
  3. 3

    Configure Continue CLI

    wavespeed setup continue

No Node.js? See other install options

Manual setup

Edit ~/.continue/config.yaml
# File: ~/.continue/config.yaml  (add this entry under models:)
name: WaveSpeed
version: 1.0.0
schema: v1
models:
  - name: "WaveSpeed deepseek/deepseek-v4.1-flash-1017"
    provider: openai
    model: "deepseek/deepseek-v4.1-flash-1017"
    apiBase: https://llm.wavespeed.ai/v1
    apiKey: "${{ secrets.WAVESPEED_API_KEY }}"
    roles:
      - chat
    defaultCompletionOptions:
      contextLength: 128000
      maxTokens: 16000

Do not replace the variable name

WAVESPEED_API_KEY is the environment variable name that the agent reads. Keep this name in the config file, and put your real API key in your shell instead.

1

Temporary for this terminal

Works until you close this terminal window.

export WAVESPEED_API_KEY="wsk_live_..."
2

Keep it after restart

Writes the key into your shell profile so new terminals can read it.

echo 'export WAVESPEED_API_KEY="wsk_live_..."' >> ~/.zshrc
source ~/.zshrc

Agent integration guide

Use Continue CLI with WaveSpeed LLM API

This guide shows how to connect Continue CLI to WaveSpeed AI with ~/.continue/config.yaml, OpenAI-compatible chat completions, /v1/chat/completions, base URL https://llm.wavespeed.ai/v1, and default model deepseek/deepseek-v4.1-flash-1017. Copy the configuration above, export your API key, run the agent, then verify requests in Logs.

1

Create a WaveSpeed access key

2

Export the required key locally

3

Paste config into

~/.continue/config.yaml
4

Run cn and check Logs

What this Continue CLI setup configures

Protocol

OpenAI-compatible chat completions

Endpoint

/v1/chat/completions

Model

deepseek/deepseek-v4.1-flash-1017

The copy-ready configuration above is the only Continue CLI file you need to edit for the recommended setup: ~/.continue/config.yaml. Keep the API key in your shell environment so it is not committed to a repository.

Troubleshooting

The API key is not being picked up

Export WAVESPEED_API_KEY in the same shell where you run Continue CLI. If you use a shell profile, reload the terminal before starting the agent.

Requests fail with a protocol or endpoint error

Check that Continue CLI is using OpenAI-compatible chat completions and endpoint /v1/chat/completions. Protocol mismatches are the most common cause of 404 or payload errors.

The selected model does not work

Confirm the model id exists in WaveSpeed Models, then paste the exact id into ~/.continue/config.yaml. You can start with the default model shown on this page.

No requests appear in Logs

Make sure Continue CLI is using the WaveSpeed base URL and your current API key. Then send a new prompt from the local agent and refresh Logs.

Can this Continue CLI guide show up in search?

Yes. This page is built as an indexable setup guide for users searching for Continue CLI custom provider, OpenAI-compatible endpoint, base URL, and local agent configuration workflows.