Continue remains an important coding tool after Cursor deal
August 4, 2026
Continue was one of the most visible open coding-agent tools for VS Code, JetBrains, and CLI. The Cursor acquisition and final 2.0.0 release make it a clear update topic.
What this is about
Continue is an AI coding tool that developers can use as a VS Code extension, JetBrains plugin, and CLI. The official website now says Continue has been acquired by Cursor. At the same time, the GitHub repository describes a final 2.0.0 release for VS Code, CLI, and JetBrains with cleaned-up authentication, removed anonymous telemetry, and bug fixes.
This is not a general market rumor, but a concrete change to a usable tool. For teams comparing open coding assistants with Cursor, GitHub Copilot, Claude Code, or Codex, Continue remains relevant, but it needs to be assessed differently than before the acquisition.
What Continue actually does
Continue lets developers use AI code agents inside the editor and terminal. The documentation describes an open system for VS Code and JetBrains where teams can create, share, and use their own agents. The GitHub repository also names the CLI as the recommended path, while the JetBrains plugin remains part of the final release.
In practice, this covers typical coding assistant capabilities: chat over code, autocomplete, contextual help, agent configuration, and model choice. The central difference from more closed offers is the emphasis on open source, custom configuration, and the ability to connect different model providers or local models.
Why it matters
AI coding tools in 2026 are no longer just autocomplete. Many teams are moving real development work into agent workflows: reading code, writing tests, preparing refactors, reviewing pull requests, and updating documentation. That is why control matters: who controls the agent, where source code is processed, and whether a team becomes locked into one provider.
Continue was attractive to many developers because it stayed close to their own toolchain: editor, repository, configuration files, and model choice. The Cursor acquisition may bring new product integration, but it also creates an open question: how long will the previous open model remain strategically important in exactly this form? Official communication emphasizes continuity, but teams should review the roadmap, repository activity, and licensing before rolling Continue out as a long-term standard.
In plain language
Continue is like a toolbox for programmers where you can place different screwdrivers yourself. Other tools often bring a finished box with fixed tools inside. Continue was especially interesting because teams could configure the box themselves. After the Cursor acquisition, teams should check whether that box remains open and which parts will be shaped by Cursor in the future.
A practical example
A software team with 18 developers uses VS Code, JetBrains, and some local models for internal repositories. It creates around 45 pull requests per week. With Continue, the team could define shared agent rules: which files count as context, which model is allowed for sensitive repositories, and which commands the agent may run.
A sensible pilot would be small: two repositories, four developers, four weeks. The team should measure not only perceived productivity, but concrete values: time to first review, number of follow-up fix commits, test coverage in changed modules, and cases where the agent made false assumptions. After the Cursor acquisition, the checklist should also include whether all required features remain usable without new platform dependency.
Scope and limits
First, Continue's open roots are not permission for uncontrolled code access. Anyone using cloud models must check which data goes to which provider and what contracts apply.
Second, the Cursor acquisition is a strategic change. It can strengthen the tool, but it can also change priorities. Teams should not rely only on old blog posts, but follow the current state of the official website, documentation, and repository.
Third, Continue does not replace engineering discipline. An agent can suggest code, but architecture decisions, security reviews, tests, and accountability remain with the team. Open configuration is powerful, but it can also be misconfigured.
SEO & GEO keywords
Continue, Continue.dev, Cursor, AI coding tool, coding agent, VS Code, JetBrains, CLI, open source AI, developer tools, code assistant, AI tools 2026
π‘ In plain English
Continue is an open coding assistant for editor and terminal. After the Cursor acquisition, it remains useful, but should be reviewed as a tool with a changed strategic position. Model choice, privacy, license, and roadmap matter most.
Key Takeaways
- βContinue is a usable AI coding tool for VS Code, JetBrains, and CLI.
- βThe official website says it has been acquired by Cursor.
- βThe GitHub repository mentions a final 2.0.0 release with anonymous telemetry removed.
- βIts value lies in open configuration, model choice, and team agents.
- βTeams should review roadmap, privacy, and Cursor dependency before rollout.
FAQ
Is Continue still usable?
Yes, the official sources still show the repository, documentation, and product page. Teams should still review the current state after the Cursor acquisition.
How is it different from Cursor?
Continue was positioned more as an open assistant for existing editors and custom configuration. Cursor is a broader AI IDE and is now also the new owner.
Why does the 2.0.0 release matter?
The repository describes it as the final release for VS Code, CLI, and JetBrains. It mentions removed anonymous telemetry and cleaned-up authentication, among other changes.
Who should consider Continue?
Developer teams that care more about model choice, local options, and configurable agents than a fully closed all-in-one solution.