Continue.dev¶

What it is¶

Continue is an open-source AI code assistant and IDE extension that enables developers to integrate frontier LLMs directly into VS Code and JetBrains. It is model-agnostic, supporting local inference (via Ollama) and remote APIs (Anthropic, OpenAI), and provides deep codebase context through a customizable "Context Provider" system.

What problem it solves¶

Continue solves the problem of vendor lock-in by providing a flexible, open-source layer between the IDE and the AI provider. It enables privacy-conscious development by allowing 100% local operation and addresses the "context awareness" challenge by providing a framework to pull in documentation, GitHub issues, and terminal logs directly into the AI's prompt.

Where it fits in the stack¶

Development & Ops / Development Environment. It acts as an extensible AI companion inside existing IDEs, serving as an open alternative to GitHub Copilot and Cursor.

Typical use cases¶

Privacy-First Coding: Using local Llama 4 or Starcoder 2 models via Ollama for enterprise development.
Context-Aware Debugging: Pulling in terminal output and recent file history automatically to help the AI diagnose errors.
Documentation Q&A: Adding specific documentation URLs as context providers to ask questions about new libraries.
Custom Workflow Automation: Defining project-specific slash commands for repetitive tasks like unit test generation or code review.
Enterprise Model Routing: Routing different tasks to different models (e.g., small models for autocomplete, large models for chat).

Strengths¶

Model Agnostic: Seamlessly switch between local and cloud providers.
Extensible Context: High-performance "Context Providers" for codebases, docs, terminal, and MCP.
Open Source: Fully transparent and community-driven, under the Apache 2.0 license.
IDE Support: Native extensions for both VS Code and the full JetBrains suite.
Customizable: Deep configuration via a standard config.json for team-wide consistency.

Limitations¶

Manual Configuration: Requires more setup effort than "turnkey" alternatives like Cursor.
UX Consistency: As an extension, it is sometimes limited by the host IDE's UI constraints compared to a standalone AI-native IDE.
Inference Speed: Local model performance is limited by the developer's hardware.

When to use it¶

When you require full control over which models are used and where your data is sent.
When you want to combine multiple model providers (e.g., local for completions, cloud for complex logic).
When you prefer to stay in your existing, highly-tuned VS Code or JetBrains environment.

When not to use it¶

If you want a zero-configuration, "it just works" experience (consider Cursor or Windsurf).
If you need a fully autonomous, terminal-first agent (consider Claude Code or Aider).

Getting started¶

Installation¶

Continue is installed via the IDE marketplace:

# VS Code
code --install-extension continue.continue

# JetBrains
# Search for "Continue" in the Settings > Plugins menu

Initial Configuration¶

Open your config.json (via the gear icon in the Continue sidebar) to define your providers.

CLI examples¶

Running the Continue Headless Indexer¶

Continue includes a CLI for indexing large repositories for team-wide use:

npx continue-index .

Updating Configuration via CLI¶

You can use the Continue CLI to manage your local config programmatically:

continue config set models.default "anthropic/claude-4-8-opus"

Checking Context Provider Health¶

Validate that your configured documentation and codebase indices are healthy:

continue doctor

API examples¶

config.json with Native MCP Support (June 2026)¶

As of June 2026, Continue supports Model Context Protocol servers directly in the configuration:

{
  "models": [
    {
      "title": "Claude 4.8 Opus",
      "provider": "anthropic",
      "model": "claude-4-8-opus-20260528"
    }
  ],
  "contextProviders": [
    {
      "name": "mcp",
      "params": {
        "url": "http://localhost:3000/mcp"
      }
    },
    {
      "name": "codebase",
      "params": {}
    }
  ]
}

Custom Context Provider (TypeScript)¶

You can build custom context providers to bridge internal company data:

export async function getCustomContext(query: string) {
  // Logic to fetch data from an internal wiki or database
  return {
    name: "InternalWiki",
    description: "Company-specific architectural standards",
    content: "All services must use the standard auth middleware..."
  };
}

Cursor — The leading AI-native IDE fork.
Zed — High-performance Rust editor with native AI features.
Aider — Terminal-native pair programmer.
Ollama — Recommended for local model serving with Continue.
Model Context Protocol — Supported for context extension.
VS Code — The primary host IDE.
Tabnine — Alternative autocomplete-focused extension.
Windsurf — IDE with persistent context "Flows".
Chronos MCP — For agentic calendar orchestration.
Free Will MCP — For AI autonomy and self-prompting.

Sources / references¶

Contribution Metadata¶

Last reviewed: 2026-06-28
Confidence: high