Continue.dev is discontinued. Time to migrate off it.
Cursor bought the team and wound the product down. The open-source code survives under Apache 2.0, but the hosted service is dead and its cloud data was deleted on 15 July.
Continue, the open-source AI coding assistant many developers ran as an alternative to GitHub Copilot, has been discontinued. Cursor acquired the team in a quiet acqui-hire and shut the product down. If your editor still runs Continue, you are now on abandoned software — and if you kept anything only in Continue's cloud, that window has already closed.
There was barely an announcement. Around 16 June, Continue's homepage was replaced with a note saying it had joined Cursor; a short FAQ told users they had until 15 July to export their data before it was deleted, and that recurring billing had been switched off. Today is past that date. Continue shipped as a VS Code extension, a JetBrains plugin and a CLI, and let you plug in your own model and pull context from tools like Jira and Confluence.
What actually survives
The code, not the service. Continue's GitHub repository is now read-only after a final 2.0.0 release, and the project's own site confirms the codebase “remains freely available as a foundation for others.” It is Apache 2.0 licensed, so existing forks and pinned builds are legal to keep running. What is gone is the hosted side: billing, account services, and any conversation history or team configs that lived on Continue's servers rather than in your own repo.
Per The New Stack, the deal was one of several Cursor tuck-ins alongside Supermaven and Graphite, and landed in the same window as SpaceX's reported $60 billion purchase of Cursor — which is roughly why a tool with tens of thousands of GitHub stars could be wound down with almost no notice.
What to do
- If you still have Continue in an editor, treat it as end-of-life. Do not start new work assuming the hosted features will keep working.
- Pick a maintained path: a supported assistant such as Copilot or Cursor, or — if you want to stay open-source and self-hosted — pin the final Apache-2.0 release or a community fork.
- Assume any cloud-stored history is gone. Going forward, keep configs in your own repo so the next vendor shutdown cannot take them with it.
Why it matters
If your team's editors run Continue's assistant, you are now on discontinued software. The hosted service is dead and cloud data was deleted on 15 July — plan a migration to a maintained tool, or pin the open-source fork you control.
Sources
- Continue has joined Cursor — Continue (primary)
- Cursor quietly acquires Continue, an open-source alternative to GitHub Copilot — The New Stack
- Cursor acquires open source coding assistant Continue — Digital Today
Reported by Software Crit from the sources above. Every story is confirmed against at least two independent publishers before publication.
Get the weekly roundup
Honest reviews, practical comparisons and the tool news that actually changes your stack.