Continue.dev

Connect the VS Code / JetBrains AI assistant through config.yaml (or legacy config.json) — chat, autocomplete and embeddings on one key

Continue is an open-source AI assistant for VS Code and JetBrains. Recent versions configure multi-model providers through ~/.continue/config.yaml; older ones use ~/.continue/config.json. Both formats are shown below.

Install#

Install the Continue extension in VS Code, or the Continue plugin in JetBrains.

Get an API key#

Create one at dianqi.zsopc.com/dashboard/keys (format: sk-gpushare- plus 64 hex characters, 76 in total; you can re-reveal it on its detail page at any time). Auth details: Authentication.

Setup (config.yaml, current)#

Edit ~/.continue/config.yaml. Chat, autocomplete and embeddings are separated by roles:

name: This platform
version: 0.0.1

models:
  - name: Claude Sonnet 4.6 via this platform
    provider: openai
    model: claude-sonnet-4-6
    apiBase: https://dianqi.zsopc.com/v1
    apiKey: sk-gpushare-xxx
    roles:
      - chat
  - name: GPT-5.4 via this platform
    provider: openai
    model: gpt-5.4
    apiBase: https://dianqi.zsopc.com/v1
    apiKey: sk-gpushare-xxx
    roles:
      - chat
  - name: DeepSeek V3.2 (autocomplete)
    provider: openai
    model: deepseek-v3.2
    apiBase: https://dianqi.zsopc.com/v1
    apiKey: sk-gpushare-xxx
    roles:
      - autocomplete

Field names (the roles values and so on) follow the Continue docs for whichever version you installed. From our side all that matters is provider: openai plus apiBase: https://dianqi.zsopc.com/v1 and your key.

Setup (config.json, legacy)#

Older versions of the extension use ~/.continue/config.json:

{
  "models": [
    {
      "title": "Claude Sonnet 4.6 via this platform",
      "provider": "openai",
      "model": "claude-sonnet-4-6",
      "apiBase": "https://dianqi.zsopc.com/v1",
      "apiKey": "sk-gpushare-xxx"
    },
    {
      "title": "GPT-5.4 via this platform",
      "provider": "openai",
      "model": "gpt-5.4",
      "apiBase": "https://dianqi.zsopc.com/v1",
      "apiKey": "sk-gpushare-xxx"
    },
    {
      "title": "GLM-5.1 via this platform",
      "provider": "openai",
      "model": "glm-5.1",
      "apiBase": "https://dianqi.zsopc.com/v1",
      "apiKey": "sk-gpushare-xxx"
    }
  ]
}

Continue reloads automatically on save and the entries appear in the model picker.

Autocomplete model (legacy)#

Under the old config.json scheme, tab autocomplete is configured separately via tabAutocompleteModel:

{
  "tabAutocompleteModel": {
    "title": "DeepSeek V3.2 (autocomplete)",
    "provider": "openai",
    "model": "deepseek-v3.2",
    "apiBase": "https://dianqi.zsopc.com/v1",
    "apiKey": "sk-gpushare-xxx"
  }
}

Use deepseek-v3.2 ($0.27/M input) or grok-4-fast-non-reasoning ($0.2/M) — autocomplete fires constantly, so a cheap small model keeps the bill sane.

Embeddings#

The platform retired its embedding SKUs in July 2026, so POST /v1/embeddings has no available model (calls return 404 model_not_found). Use a local option for Continue's codebase indexing — for example Ollama's nomic-embed-text (fully offline and free). Under the new config.yaml scheme, don't add a roles: [embed] entry pointing at this platform.

What actually goes through the gateway#

Continue's chat and autocomplete requests use the OpenAI Chat protocol, so the available models are every text model returned by GET /v1/models (60+ and growing; models without a native OpenAI-protocol channel are translated automatically by the gateway). See the compatibility matrix and Models.

Troubleshooting#

SymptomWhat to check
Model missing from the dropdownconfig.yaml / config.json syntax — Continue silently ignores invalid model entries
401 (invalid_api_key)Key invalid, revoked or expired. Check you copied the whole thing (sk-gpushare- plus 64 hex characters); the full key can be re-revealed on the console detail page
400 (model_not_found / model_not_allowed)Check the model field is a real catalog model ID. model_not_allowed means this key has an allowed_models allowlist — edit it in the console or use an unrestricted key
402 (insufficient_quota, code quota_exceeded)Account balance exhausted. All keys share one balance so a new key won't help → top up at dflop.top/dashboard/billing (Stripe, $1 minimum). High-frequency autocomplete burns balance fast — switch to deepseek-v3.2 to control it
Autocomplete is expensiveSwitch to deepseek-v3.2 or grok-4-fast-non-reasoning

Full error reference: Error handling.

Other clients#