Continue Dev · Tools

Continue

Visit website

At a glance

Price
Pricing on request
Vendor
Continue Dev

Specifications & properties

Key decision factors

Pricing model
Open source 1
Tool form
  • IDE plugin
  • CLI agent
1
Autonomy level
Supervised agent 1

Pricing

Price from
Pricing on request 1
Free tier
Yes 1

Integration

IDE integrations
  • VS Code
  • JetBrains
1
Report data / suggest a correction

Continue is an open-source coding agent available as a CLI, VS Code extension, and JetBrains plugin; the company has been acquired by Cursor.

Profile

Continue is an open-source AI coding assistant — available as a VS Code extension, a JetBrains plugin, and a command-line tool — that was built to be model-agnostic, letting developers plug in almost any large language model (local models via Ollama, or cloud models from OpenAI, Anthropic, Mistral, and others) for autocomplete, chat, and agentic coding tasks. Continue Dev, Inc. released the project under an Apache 2.0 license starting in 2023, and the codebase grew to roughly 34,800 GitHub stars and 5,000 forks before development effectively stopped.

Current status: acquired and discontinued

As of mid-2026, Continue is no longer an actively developed, independent product. Continue's own homepage now states plainly: 'Continue has been acquired by Cursor.' According to reporting on the deal, Cursor (legal name Anysphere) quietly acqui-hired the Continue team around June 16, 2026, and the companies did not disclose financial terms. Continue shipped a final v2.0.0 release of its VS Code extension, CLI, and JetBrains plugin — removing anonymous telemetry and authentication code, and fixing bugs — around June 19, 2026, and the GitHub repository (continuedev/continue) is now marked no longer actively maintained and read-only for all users. Notably, the same week Cursor announced the Continue acquisition, SpaceX announced it would acquire Cursor itself for $60 billion in an all-stock deal placing it under xAI, a deal expected to close in Q3 2026 — meaning Continue's code now sits several acquisitions deep inside a very different kind of company than the one that built it.

What it did / what remains usable

Before the acquisition, Continue's core features were tab-autocomplete using fill-in-the-middle (FIM) models, an in-editor chat interface, code editing that preserves formatting and style, and an agent mode capable of autonomous multi-step tasks with tool use. Configuration happened through a config.yaml (or config.json) file that let teams define separate models for chat, edit, apply, embed, and rerank roles, and Continue could run entirely offline against locally hosted models for teams that wanted no code leaving their network. Because the code remains published under Apache 2.0 and the repository, while read-only, is still publicly accessible, existing forks, pinned builds, and self-hosted deployments of Continue can, in principle, keep running — there is simply no ongoing development, support, or roadmap from the original team.

Who it's for now

Given the acquisition and discontinuation, Continue is best understood today as a snapshot of an open-source, model-agnostic coding-assistant architecture rather than an actively maintained product to adopt going forward. Teams that already depend on it may continue running it via self-hosted or forked builds, but anyone newly comparing coding assistants should treat Continue as a historical/legacy option and look at Cursor (its acquirer) or other actively maintained alternatives for new projects.

Frequently asked questions

Is Continue still available / is it free?

The open-source code is still available for free under the Apache 2.0 license, but Continue is no longer an actively developed product — it was acquired by Cursor around June 16, 2026, shipped a final v2.0.0 release, and its GitHub repository is now read-only.

What happened to Continue.dev?

Cursor (Anysphere) acquired Continue's team in June 2026 and wound down the standalone product; Continue's own homepage now states 'Continue has been acquired by Cursor,' with no further updates planned from the original team.

Can Continue still be self-hosted or run offline?

Yes in principle — Continue was designed to run entirely against local models (e.g. via Ollama) with no code leaving the network, and since the code remains published under Apache 2.0, existing forks and pinned builds can still be self-hosted, though without official support going forward.

Which IDEs did Continue support?

Continue was available as a VS Code extension, a JetBrains plugin, and a command-line tool.

Is Continue model-agnostic — can I use my own LLM?

Yes — Continue's config.yaml let teams assign different models to chat, edit, apply, embed, and rerank roles, supporting local models via Ollama as well as cloud providers like OpenAI, Anthropic, and Mistral.

What is Continue best for today?

Given the Cursor acquisition and discontinuation of active development, Continue is best suited to teams already running self-hosted or forked deployments who want to keep them going, rather than as a first choice for a new AI-coding-assistant setup.