Cursor has acquired Continue, the open-source coding assistant that let developers build their own AI pair programmer on top of any model. The deal, reported June 22, 2026, folds one of the best-known alternatives to GitHub Copilot into Cursor, and it comes with a hard deadline that existing Continue users need to act on.

What Happened

Continue confirmed the acquisition with a brief notice on its homepage and an FAQ for current users. The startup, a Y Combinator graduate, shipped a final 2.0.0 release and has stopped active development. Terms were not disclosed. The acquisition was signed in the same window as SpaceX's reported $60 billion purchase of Cursor, which means Continue now sits under that larger umbrella too.

Why It Matters

Continue was the go-to for developers who wanted a customizable assistant rather than a closed product. It ran as a VS Code extension, a JetBrains plugin, and a CLI, and it let teams plug in their own models and pull context from tools like Jira and Confluence. Its GitHub repository, with more than 34,000 stars, has now been switched to read-only. The acquisition is the latest move in a fast-consolidating AI coding-tools market, and it narrows the field of independent, model-agnostic assistants. For teams that standardized on Continue precisely because it was not locked to a single vendor, the change forces a rethink of how their assistant is configured and where their context lives.

Key Details

The most urgent detail is the data deadline: existing Continue users have until July 15, 2026 to export their data, after which it will be deleted. The open-source code remains available under its existing license on GitHub, but no new features are coming, and the read-only flag means community pull requests can no longer be merged. Continue's blog remains the reference point for migration notes and the final changelog. Anyone running Continue in a team setting should treat the 2.0.0 build as the last stable version and plan around it accordingly.

What to Do Next

If you run Continue, export your configurations, prompt libraries, and any custom assistants before July 15. Then pick a replacement: Cursor itself is the obvious migration path, and our look at Cursor's Origin git forge and the GitHub Copilot auto model routing update can help you weigh the options. For background on the larger deal, see our report on SpaceX acquiring Cursor.