agent
Open source
free (BYO API key)
4.4/5

Continue

Open-source VS Code and JetBrains assistant. Configurable autocomplete + chat + agent modes. Strong with local Ollama backends.

By Eruo Fredoline·Last verified Oct 7, 2026·25,000 GitHub stars

Overview

Open-source VS Code and JetBrains assistant. Configurable autocomplete + chat + agent modes. Strong with local Ollama backends.

Setup guidance

Install as a VS Code or JetBrains extension. VS Code: Extensions panel (Ctrl+Shift+X), search "Continue", install. JetBrains: Plugins marketplace, search "Continue", install. Continue is an open-source AI code assistant that works as an IDE extension, connecting to any LLM provider (cloud API or local). After install, open the Continue sidebar (Ctrl+L / Cmd+L or the Continue icon). On first launch, Continue walks through model configuration: pick a provider (Anthropic, OpenAI, local, Ollama, etc.), enter API key if needed, and select a chat model. For local models via Ollama: select "Ollama" as provider, set model to llama3.2, and ensure ollama serve is running. The chat interface supports @file, @folder, and @code context references — drag files into chat for context. Tab autocomplete: enable in Continue settings (powered by smaller, faster models — Starcoder, CodeLlama, Codestral). Verify: type a comment like // create a function that sorts by date and press Tab — Continue inserts completion. Time-to-first-response: ~5 seconds for chat, ~200ms for tab completions. All configuration lives in .continue/config.json (per-project) or global settings.

Workload fit

Best for: developers who want provider flexibility — use local models for tab completions and cloud models for complex chat within the same tool, teams with multiple LLM providers or model preferences that need a single consistent IDE extension, VS Code + JetBrains dual-IDE users who want the same AI tool across both, open-source shops that prioritize self-hosted code assistant tooling, developers who prefer extensible, config-file-driven tools over managed platforms. Not suited for: developers who want zero-config setup (use Cursor or GitHub Copilot), autonomous agentic coding where the AI creates files and runs commands (use Cline or Claude Code), non-developer team members (Continue assumes IDE literacy).

Alternatives

Use Continue when you want an open-source, provider-flexible AI assistant that works across VS Code and JetBrains — connect any LLM (cloud or local), any model, any tab-completion backend. Switch to Cursor when you want a fully integrated AI-native IDE with polished inline editing and agent mode — Continue is an extension, Cursor is a platform. Use Cline when you want autonomous agentic coding inside VS Code — Continue is assistive (chat + completions), Cline is agentic (file creation, terminal execution, autonomous loops). Use GitHub Copilot for the simplest "just works" completions across every IDE — Continue requires initial model configuration. Use Aider for terminal-based pair programming with git diff workflow — Continue is IDE-integrated. Continue's key advantage: provider independence. You can switch from OpenAI to Anthropic to local Llama without changing tools. Its weakness: setup friction compared to managed solutions.

Troubleshooting + when to switch

Problem: Tab completions never appear or are extremely slow (>1 second). Fix: Continue's tab model is configured separately from the chat model. In config.json, check the "tabAutocompleteModel" object has correct provider and model settings. Tab autocomplete needs low latency — use a smaller model (Starcoder 3B, Codestral 7B) locally or a fast API. If using a local model, ensure it's loaded and responsive before expecting completions. Problem: @file references return "No context found." Fix: Continue indexes files referenced with @file using the file path relative to the workspace root. If the file path includes spaces or special characters, wrap in quotes: @"file with spaces.ts". The file must exist on disk. For large files, Continue may truncate context — it respects a configurable max-chars limit. Problem: Chat model switch doesn't take effect. Fix: Continue caches model config at startup. After changing config.json, reload: Cmd+Shift+P → "Continue: Reload Config." The chat interface shows the active model — verify the switch took effect. Some model names differ between providers ("claude-4" vs "claude-sonnet-4-20250514"). Check provider docs for exact model IDs.

Stack & relationships

How Continue relates to other entries in the catalog — recommended pairings, alternatives, dependencies, and edges to avoid. Each edge carries a one-line operator note from our editorial team.

Continue ↔ ecosystem

Recommended stack

  • Commonly deployed with
    Ollama

    Continue's IDE integration assumes a local OpenAI-compatible endpoint; Ollama is the canonical pairing for individual developers.

Alternatives

  • Competes with
    Cline

    Both are VS Code-native agents. Continue is the older, broader project; Cline is more focused on autonomous task execution.

  • Alternative to
    Cline

    Both are VS Code-native. Continue is broader (chat + autocomplete + commands); Cline is focused on autonomous task execution. Pick Continue for everyday IDE help; Cline for autonomous tasks.

Pros

  • Open source
  • Local-first model story
  • VS Code + JetBrains

Cons

  • UX less polished than Cline/Cursor

Compatibility

Operating systems
macOS
Linux
Windows
GPU backends
n/a (uses cloud or local API)
LicenseOpen source · free (BYO API key)

Runtime health

Operator-grade signals on how actively Continue is being maintained, how fresh its measurements are, and what failure classes operators have flagged. Every label below is anchored to a real date or count — we never infer maintainer activity we can't show.

Release cadence

Derived from the most recent editorial signal on this row.

Active
Updated Oct 7, 2026

28 days since last refresh · source: lastUpdated

Benchmark freshness

How recent the editorial measurements on this runtime are.

0editorial benchmarks

No editorial benchmarks for this runtime yet.

Community reproduction

Submissions that match an editorial measurement on similar hardware.

0reproduced reports

No community reproductions on file yet.

Ecosystem stability

Editorial rating from RunLocalAI — qualitative, not measured.

4.4/5Editorial

Get Continue

Frequently asked

Is Continue free?

Yes — Continue is free to use and open-source.

What operating systems does Continue support?

Continue supports macOS, Linux, Windows.

Does Continue need a GPU?

No — Continue runs on CPU; it does not require or use a GPU.

Reviewed by RunLocalAI Editorial. See our editorial policy for how we evaluate tools.

Related — keep moving

Recommended hardware
Before you buy

Verify Continue runs on your specific hardware before committing money.