RUNLOCALAIv38
->Will it run?Best GPUCompareTroubleshootStartLearnPulseModelsHardwareToolsBench
Run check
RUNLOCALAI

Independently operated catalog for local-AI hardware and software. Hand-written verdicts. Source-cited claims. Reproducible commands when we have them.

OP·Fredoline Eruo
DIR
  • Models
  • Hardware
  • Tools
  • Benchmarks
TOOLS
  • Will it run?
  • Compare hardware
  • Cost vs cloud
  • Choose my GPU
  • Prompting kits
  • Quick answers
REF
  • All buyer guides
  • Learn local AI
  • Methodology
  • Glossary
  • Errors KB
  • Trust
EDITOR
  • About
  • Author
  • How we make money
  • Editorial policy
  • Contact
LEGAL
  • Privacy
  • Terms
  • Sitemap
MAIL · MONTHLY DIGEST
Get monthly local AI changes
Monthly recap. No spam.
DISCLOSURE

Some links on this site are affiliate links (Amazon Associates and other first-class retailers). When you buy through them, we earn a small commission at no extra cost to you. Affiliate links do not influence our verdicts — there are cards we rate highly that we don't have affiliate relationships with, and cards that sell well that we refuse to recommend. Read more →

© 2026 runlocalai.coIndependently operated
RUNLOCALAI · v38
  1. >
  2. Home
  3. /Learn
  4. /How-to
  5. /How to use Continue.dev to connect a local codebase to a custom LLM backend
HOW-TO · DEV

How to use Continue.dev to connect a local codebase to a custom LLM backend

intermediate·15 min·By Fredoline Eruo
Target environment
Ubuntu 24.04 · Continue.dev 0.9.x
PREREQUISITES

Continue.dev installed, LLM backend running

What this does

Continue.dev is an open-source VS Code and JetBrains extension that provides an AI coding assistant powered by any LLM. By connecting Continue.dev to a local LLM backend (such as Ollama or LM Studio), developers keep code entirely on-premises while retaining full AI-assisted navigation, editing, and search capabilities.

Steps

  1. Open the Continue.dev configuration file at ~/.continue/config.json using a text editor.
  2. In the models array, add a new entry with "provider": "openai" (Continue uses OpenAI-compatible API shape) and "model": "local-model".
  3. Set "api_base": "http://localhost:11434/v1" to point to the local Ollama proxy.
  4. If the backend requires an API key, set "api_key": "ollama" (Ollama does not validate the key field).
  5. Save the configuration and reload the IDE window.
  6. Open the Continue.dev side panel and verify that the model selector dropdown shows the newly added local model.
  7. Select the local model from the dropdown and send a simple prompt such as "List the files in this project" to confirm it responds.
  8. Confirm that responses reference the actual project files to verify context injection is functioning.

Verification

curl -s http://localhost:11434/api/tags | python3 -c "import sys,json; models=json.load(sys.stdin)['models']; print('Models available:', len(models), '| First:', models[0]['name'] if models else 'none')"

Expected output: a line showing the count of available models and the name of at least one model, confirming the backend is reachable.

Common failures

  • Connection refused: Ensure the LLM backend process is running and the port matches the api_base URL in the config.
  • Model not loaded: Run ollama pull <model-name> before attempting to use the model in Continue.dev; the backend must have the model filesystem available.
  • Context window errors: Reduce the context size in the Ollama configuration or lower maxTokens in config.json to prevent overflow on large codebases.

Related guides

  • How to configure Continue.dev with multiple AI providers and switch between them
  • How to use Continue.dev codebase index for fast semantic search across your project
← All how-to guidesCourses →