Continue.dev Is Dead: What Happened and the Best Alternatives After the Cursor Acquisition

Short answer: Continue.dev no longer exists as an active product. Cursor acquired it in mid-June 2026, shipped a final v2.0.0 release on June 19, and set the continuedev/continue GitHub repository to read-only. The data export deadline was July 15, 2026 — already passed. If you're looking for "the best free BYOK extension with full JetBrains support" (which used to be Continue), the honest answer today is a combination: Cline for VS Code (with JetBrains in Early Access), Kilo Code for broader JetBrains BYOK support, or terminal-native Aider if you don't need an IDE at all.

What Actually Happened, With Dates

The deal terms were never disclosed. Coverage consistently characterizes it as an acqui-hire — Cursor took the team and the ideas; the standalone product was shut down rather than integrated as-is. Continue entered the deal as a Y Combinator Summer 2023 company with roughly 34,000+ GitHub stars, ~21,500 commits, and about $5 million raised.

The same week, Cursor itself was absorbed into a larger deal: on June 16, 2026, SpaceX announced it would acquire Cursor's parent company Anysphere for $60 billion, placing Continue's former codebase under an ownership chain that now runs Continue → Cursor → SpaceX/xAI. See our July 2026 roundup for the full context of that acquisition and the Windsurf → Devin Desktop rebrand that happened the same month.

Why This Specifically Hurts JetBrains + BYOK Users

Continue's specific value proposition — full-featured inline autocomplete, chat, and agent mode, BYOK, in both VS Code and every major JetBrains IDE, configured via a version-controllable YAML file — was genuinely uncommon. Most BYOK tools are VS Code-first with JetBrains as an afterthought (if supported at all). Losing Continue removes the cleanest option for developers who specifically wanted BYOK pricing and JetBrains autocomplete together in one production-stable tool.

What to Actually Do If You Were Using Continue

1. Your existing setup will keep working — for a while

The extension itself doesn't stop functioning the moment the repo went read-only. Your configured providers and models will keep working until something upstream breaks it — a VS Code extension API change, a model provider deprecating an API version, or a security issue nobody patches. There's no fixed expiration date, but treat it as living on borrowed time.

2. If your model provider's data is still on Continue Hub, export it now

The July 15, 2026 export deadline for Continue Hub's cloud-hosted data (shared prompts, team configuration, centralized settings) has passed. If you had Team or Company tier data there and haven't already retrieved it, it may already be gone — check directly rather than assuming.

3. Migrate your config, don't just uninstall

Continue's YAML-based provider configuration doesn't transfer automatically to any replacement tool — you'll need to recreate your model connections, API keys, and any custom context providers or slash commands manually in whatever you switch to.

Best Continue Replacements, By What You Actually Needed

Cline — The Default Recommendation

Cline is the consensus first choice across nearly every "what replaces Continue" discussion since the acquisition. It's Apache 2.0, free, BYOK, supports 30+ providers plus local Ollama, and has 63,000+ GitHub stars with 5M+ installs. The tradeoff versus Continue is form factor: Cline has zero inline autocomplete (it's purely an agent, working through a sidebar panel), and its JetBrains support remains Early Access rather than the production-stable plugin Continue offered. See our full Cline breakdown and Cline vs Aider comparison for more.

Kilo Code — Best for JetBrains-Heavy Teams

Kilo Code has confirmed JetBrains support alongside VS Code and CLI, plus access to 500+ models via its zero-markup Kilo Gateway. It's the strongest BYOK option specifically for teams that were relying on Continue's cross-IDE reach, though it inherited its architecture from the Roo Code/Cline lineage rather than Continue's, so configuration won't feel identical.

Aider or OpenCode — If You're Willing to Drop the IDE Panel

If Continue's chat-panel-in-the-editor experience isn't essential and you're comfortable working from a terminal alongside your editor, Aider offers the most refined git-native workflow with 5–10× lower token costs on routine edits via diff-based editing. OpenCode (MIT licensed, 150,000+ stars, 75+ model providers) is the broadest-model alternative for the same terminal-first approach.

The Broader Pattern: 2026's Consolidation Wave

Continue isn't an isolated casualty. In the same window: Roo Code was archived in May 2026 (superseded by Kilo Code), Windsurf was rebranded into Devin Desktop after Cognition's acquisition (Cascade retired), and Cursor itself is being absorbed by SpaceX/xAI. The open-source AI coding tool landscape consolidated meaningfully faster in mid-2026 than most published "2026 comparison" articles have caught up with — a pattern worth remembering whenever you're evaluating a tool based on an article that might already be a few months stale.

FAQ

Is Continue.dev still safe to use?

It will continue functioning for now, since the extension itself doesn't stop working the moment a repository goes read-only. But no one is shipping security patches, provider-API compatibility fixes, or new model support. Treat any existing Continue installation as a tool on borrowed time, not a supported product.

Can I still download Continue.dev?

The final release, v2.0.0, is technically still on GitHub since the repository (while read-only for new commits) remains publicly accessible under its Apache 2.0 license. There's no active distribution channel, marketing site, or support from the original team — you'd be installing an end-of-life build.

Why did Cursor acquire Continue if it was just going to shut it down?

Coverage consistently frames this as an acqui-hire: Cursor's interest was in the team and their expertise, not in operating Continue as a separate product. This is common in AI-tooling consolidation — the acquiring company absorbs talent and ideas into its own commercial roadmap rather than maintaining a competing open-source product.

Is there an irony in Continue being acquired by Cursor specifically?

Many in the developer community have noted it: Continue's whole value proposition was being open, BYOK, and not a subscription — the opposite of Cursor's paid, closed, credit-based model. Developers who specifically chose Continue to avoid a subscription tool like Cursor may find "the mission continues through Cursor" a strange resolution.

What's the single best replacement if I just want to switch fast?

For most former Continue users, Cline is the fastest, most direct switch — same open-source, BYOK, VS Code extension model, and it's the tool most other guides converged on recommending after the shutdown. The tradeoffs are no inline autocomplete and JetBrains support that's still Early Access rather than production-stable.

Does Kilo Code or Cline support Continue's YAML-based team configuration?

No — neither tool uses Continue's specific configuration format. You'll need to manually recreate your provider connections, API keys, and any custom prompts or context providers in whichever tool you migrate to. There's no automated migration path from Continue's format.

Bottom Line

Continue.dev is over as an actively developed product. If you're still running it, it will keep working until it doesn't — plan a migration rather than waiting for a breaking change to force one. For most developers, Cline is the closest direct replacement for the VS Code experience, Kilo Code is the stronger pick if JetBrains support matters most, and Aider is worth considering if you're open to a terminal-first workflow instead.

→ Browse the full directory to compare all 89 active alternatives by price, IDE support, and BYOK availability. See our full BYOK tools guide for the complete current landscape.