Skip to main content
Continue talks to Eden AI through its openai provider and the OpenAI-compatible /v3 base URL, so you only add models to your config.yaml.

Overview

Continue is an open-source code assistant for VS Code and JetBrains IDEs. Each model you add to its config.yaml appears in the model dropdown, and a roles list decides whether Continue uses it for chat, edits, autocomplete or embeddings. One Eden AI key and one apiBase cover all of them.

Prerequisites

  • Continue installed from your IDE marketplace: in VS Code, search for “Continue” in Extensions; in JetBrains, open Settings (Ctrl+Alt+S / Cmd+,), select Plugins and search for “Continue”
  • An Eden AI API key from app.edenai.run

Setup

Step 1: Open the config file

Open the configs dropdown in the Continue panel and click the gear icon next to your local config (Main Config on a fresh install). config.yaml opens in your editor (on a fresh install it is ~/.continue/config.yaml, or %USERPROFILE%\.continue\config.yaml on Windows). Continue 2 prefers config.yaml. If one exists, a config.json next to it is ignored, so do not edit the JSON file.

Step 2: Add Eden AI models

Replace the empty models: [] in the file with these entries (the file already has name, version and schema; keep them):
provider: openai makes Continue send OpenAI-style requests to apiBase. useLegacyCompletionsEndpoint: false keeps autocomplete and edits on /v3/chat/completions, because Continue otherwise calls the legacy /completions route, which Eden AI does not serve. Continue guesses whether a model supports tools from its id, and that guess fails for provider/model ids, so capabilities: [tool_use] turns on native tool calling for Agent mode.

Step 3: Store your key

The ${{ secrets.EDEN_AI_API_KEY }} reference keeps the key out of the config. Continue looks it up in ~/.continue/.env, then in the .env files of your workspace, then in the process environment. Create ~/.continue/.env:

Step 4: Save

Save config.yaml. Continue reloads it automatically and the new models appear in the model dropdown.

Model naming

Use the full provider/model id as model, such as anthropic/claude-sonnet-latest, openai/gpt-latest or openai/gpt-mini-latest. Aliases ending in -latest follow the newest model of a family. A model you use in Agent mode needs function calling; see Listing models for each model’s capabilities.

Embeddings

The embed role in the config above sends Continue’s embedding requests to Eden AI’s /v3/embeddings. Use an id from the embeddings catalog, such as openai/text-embedding-3-small.

Expert Models as Tools (MCP)

Eden AI also hosts an MCP server that exposes the expert model catalog (OCR, web search, speech, translation and more) as tools. Add the server to your assistant’s config.yaml:
The tools become available in Agent mode. See the MCP server page for the full tool catalog and the conventions its tools share.

Troubleshooting

Models Not Appearing

If models don’t appear in the dropdown:
  1. Check that config.yaml is valid YAML and that each model has name, provider and model. Config errors appear in the Configs section of Continue’s settings.
  2. Ensure apiBase is exactly: https://api.edenai.run/v3

Authentication Errors

If you see 401 errors:
  1. Verify the key in ~/.continue/.env (or in the .env file your secrets reference reads)
  2. Check there are no extra spaces in the API key
  3. A 401 with Invalid API key means the sk-eden-... key is wrong or revoked; Invalid token means the credential is not an Eden AI key at all.
  4. Test the API key manually:

Agent mode does not call tools

Add capabilities: [tool_use] to the model, and use a model that supports function calling.

Next Steps