Cursor acquires Continue, its open-source rival

Key Takeaways

• Cursor has acquired Continue, an open-source AI coding assistant with over 70,000 GitHub stars
• Continue will remain open source after the acquisition, addressing community concerns
• The deal consolidates two major players challenging GitHub Copilot's dominance

Cursor has acquired Continue, the open-source AI coding assistant that built a following as a privacy-focused alternative to GitHub Copilot. The deal, announced quietly this week, brings together two of the fastest-growing challengers to Microsoft's dominant coding tool.

Continue has accumulated over 70,000 stars on GitHub and more than 500,000 VS Code installs. Developers gravitated toward it because it let them connect their own AI models, including locally-run LLMs, instead of being locked into a single vendor. That flexibility made it popular with enterprises worried about sending proprietary code to third-party APIs.

Cursor, built by Anysphere, takes a different approach. It is not a plugin but a standalone AI-first code editor forked from VS Code. Rather than just autocompleting lines, Cursor reads entire codebases and lets developers chat with their projects. The company raised over $60 million in its Series A and has become the default editor for a vocal slice of the developer community.

Why did Cursor buy an open-source competitor?

On the surface, Continue and Cursor solve similar problems. Both help developers write code faster with AI. But they target different segments. Continue appeals to teams that want control over their AI stack. Cursor appeals to individuals who want the deepest possible AI integration out of the box.

Acquiring Continue gives Cursor a foothold in the enterprise market. Companies running sensitive codebases often reject SaaS tools that route code through external servers. Continue's architecture, which supports local models and self-hosted deployments, solves that objection. Cursor can now offer those customers a path into its ecosystem without forcing them to change their security posture.

There is also the community angle. Continue's 70,000 GitHub stars represent tens of thousands of engaged developers. Many of them contribute code, file issues, and evangelize the project. That kind of organic reach is expensive to build from scratch.

Will Continue stay open source?

The announcement confirmed that Continue will remain open source. This matters. Open-source projects that get acquired sometimes pivot to restrictive licenses or stop accepting outside contributions. HashiCorp's relicensing of Terraform in 2023 taught the community to ask this question early.

Keeping Continue open source makes strategic sense for Cursor. The project's value comes partly from its community. Close the source and developers will fork it, as they did with Terraform's OpenTofu spinoff. Cursor would inherit a shrinking asset instead of a growing one.

The more interesting question is how deeply the two products will integrate. Continue currently works as a VS Code and JetBrains extension. Cursor is a standalone editor. Could Cursor embed Continue's model-agnostic backend while keeping its own frontend? Could enterprise customers run Cursor's interface with Continue's local inference? The technical possibilities are broad.

What this means for GitHub Copilot

GitHub Copilot still leads the market. Microsoft bundles it with VS Code, integrates it with GitHub, and backs it with OpenAI's models. Most developers who use an AI coding assistant use Copilot.

But Copilot's dominance is not inevitable. Developers increasingly want choice in which models power their tools. Some prefer Claude for reasoning tasks. Others want to run Llama locally. Copilot locks users into OpenAI's models, which creates an opening for more flexible alternatives.

Cursor and Continue, combined, now offer that flexibility at two levels. Individual developers can use Cursor's polished editor. Enterprises can deploy Continue's open-source stack on their own infrastructure. Neither option requires committing to a single model provider.

The AI code assistant market is projected to exceed $2.5 billion by 2027. Microsoft will not cede that ground easily. But consolidation among challengers suggests the competition is moving past the experimental phase into a real product battle.

The broader pattern in AI tooling

This acquisition fits a larger trend. AI developer tools are consolidating quickly. Startups that built point solutions are getting absorbed by companies that want to own more of the workflow. The logic is simple: developers dislike context switching. A tool that handles autocomplete, chat, code review, and documentation will beat four separate tools that each do one thing.

Cursor is betting that developers want an AI-native editor, not an AI plugin for an existing editor. Acquiring Continue strengthens that bet by adding enterprise credibility and a model-agnostic backend. Whether that combination can unseat Copilot remains an open question. But Cursor is now better positioned to try.

Frequently Asked Questions

Is Continue still free after the Cursor acquisition?

Yes. Cursor confirmed that Continue will remain open source. Users can continue using it without paying, and the project will still accept community contributions.

Can I use Continue with local AI models?

Yes. Continue supports connecting to local LLMs, self-hosted models, and various cloud providers. This flexibility was a key reason for its popularity and will continue post-acquisition.

How is Cursor different from GitHub Copilot?

Cursor is a standalone code editor built around AI, not a plugin. It offers deeper codebase understanding and chat-based coding. Copilot is an extension that adds autocomplete to existing editors like VS Code.

Will Continue be merged into Cursor?

The companies have not announced specific integration plans. For now, Continue will continue operating as a separate open-source project with its own roadmap.

What IDEs does Continue support?

Continue works as an extension for VS Code and JetBrains IDEs like IntelliJ IDEA, PyCharm, and WebStorm.

Source: The New Stack / Paul Sawers