Continue remains relevant as a codebase after Cursor acquisition

What this is about

Continue was one of the better-known open tools for AI-assisted development in VS Code, JetBrains, and CLI workflows. On 2026-06-28, the official website showed that Cursor had acquired Continue. That matters to users because it is not just company news: it changes the future of a concrete coding tool people can actually use.

The Continue site says the open-source codebase should remain available. The GitHub repository also points to a final 2.0.0 release for the VS Code extension, CLI, and JetBrains plugin. That makes this an update article rather than a normal first-time tool check.

What Continue actually does

Continue offers features developers expect from modern coding assistants: an agent for development tasks, chat over code, editing selected code sections, and autocomplete. The Visual Studio Marketplace lists more than 3.4 million installs and describes Continue as a leading open-source AI code agent.

The final 2.0.0 release matters because, according to the repository, it removed anonymous telemetry, pulled out authentication, and fixed bugs. That changes the practical question: users should check whether the final version is stable enough, which parts will keep being maintained, and whether moving to Cursor or a fork makes more sense.

Why it matters

Open-source developer tools depend not only on code, but on maintenance. When a tool is acquired, teams need to ask three questions: will the extension stay secure, will it remain compatible with editor updates, and is there enough community support if the original company invests less?

Continue has not become worthless. An Apache 2.0 codebase with many installs can remain a reference, fork base, or internal tool. For companies, this moment is exactly when a decision is needed: do not uninstall blindly, but do not ignore the change either.

In plain language

Continue is like a good cordless screwdriver whose manufacturer has been sold. The screwdriver still works today, and some replacement parts are openly available on the workbench. But if a business uses it every day, it should check whether batteries, bits, and repair support will still be reliable in six months.

A practical example

A 35-person engineering team uses Continue in VS Code and JetBrains. Each week it produces about 120 small AI edits and 40 chat-assisted code explanations. After the acquisition, the team freezes the final 2.0.0 version in its tool list, checks the telemetry change, tests the CLI on five standard repositories, and decides after 30 days whether to keep using it, maintain an internal fork, or move to Cursor, Cline, goose, or another agent.

Scope and limits

• The acquisition does not automatically mean Continue is unsafe or unusable.
• At the same time, the future of official development is less clear than before the acquisition.
• Teams should not bind sensitive repositories to an unmaintained editor plugin without an update and security plan.

SEO & GEO keywords

Continue, Cursor, open source coding agent, VS Code AI, JetBrains AI plugin, AI coding assistant, developer tools, Apache 2.0, code agent, CLI coding agent, tool migration, AI developer workflow