Continue Review 2026: Acquired by Cursor — What Happens Now
Continue was the leading bring-your-own-model coding agent for VS Code and JetBrains — open source, self-hostable, and the default answer for teams that could not send their codebase to a vendor. Then continue.dev turned into a farewell page. The repository, meanwhile, is still shipping commits. Here is what is actually left to adopt in 2026.
Quick Verdict
Best for: Teams with a hard self-hosting requirement and the engineering capacity to maintain a fork, and anyone who wants to read a mature open-source coding agent to build their own. Skip it if you need a supported product with a roadmap — the rating reflects the acquisition, not the software.
The Headline: Continue Has Joined Cursor
Visit continue.dev today and you do not get a product page. You get a notice that Continue was acquired by Cursor, a thank-you to the community for helping build what it calls a pioneering open-source coding agent, and a three-question FAQ: is the open source still available, what happened to my data, and what about my subscription. The framing is that the mission — developers amplified, not automated — carries on in the work ahead.
That third FAQ is the tell. A project with a subscription question to answer had a hosted layer, and hosted layers are what tend not to survive acquisitions. Code survives; services get folded in. If you are running Continue against its hosted account system rather than purely self-hosted, that is the dependency to audit first.
The good news is concrete and checkable. The repository at continuedev/continue is public, Apache-2.0, and not archived. At the time of writing it showed 35,607 stars, 5,279 forks, 941 open issues, and a commit that landed the same day. The statement that the codebase remains freely available as a foundation for others is, so far, accurate rather than aspirational.
Building the coding agent Continue users are migrating to? This is the page they read on the way out.
Add it to the coding category — a free listing publishes after review, and it is the same page ChatGPT, Perplexity and Google read when a developer asks for an open-source Continue alternative. Want it live in minutes with a Verified badge instead? That option is on the form, one-time, no subscription.
What Continue Did, and Why People Chose It
Continue was an AI code assistant that lived inside the editor you already used — VS Code or JetBrains — and let you point it at whatever model you wanted. A frontier API when you needed capability, a cheap fast model for autocomplete, or open weights running locally when the code could not leave the building. Autocomplete, chat, and refactoring, all on infrastructure you chose.
That last part is why it mattered. Commercial coding assistants make the model choice for you and route your source through their pipeline. For a bank, a defence contractor, a health system, or anyone under a data-residency rule, that is not a preference — it is a hard block. Continue was the answer, and dual editor support meant the JetBrains half of the team was not left out, which most competitors never bothered with.
Worth being clear about one thing the marketing never quite said: open source did not mean free. Bring-your-own-model means bring-your-own-bill. You either pay an inference provider per token or buy hardware to serve open weights. The licence cost nothing; the running cost was always real, and post-acquisition it now includes maintenance you may be doing yourself.
Continue Pros & Cons
✓ Pros
- •The code is genuinely still available — the repo is Apache-2.0, not archived, and had commits landing on the day this review was written
- •35,607 stars and 5,279 forks means the codebase will not vanish; even if upstream stops, forks are already distributed at scale
- •Bring-your-own-model was always the point: it runs against any LLM, hosted or local, rather than locking you into one vendor's inference
- •Works in both VS Code and JetBrains, which is rare — most coding agents pick one editor family and ignore the other
- •Self-hosting means code and prompts never have to leave your infrastructure, which is the reason regulated teams adopted it in the first place
- •Apache-2.0 is a permissive licence with a patent grant, so a company can fork and maintain its own build without legal ambiguity
- •The autocomplete, chat and refactor surfaces are mature — this was a finished product, not an early prototype, at the point of acquisition
- •For anyone building their own coding agent, it is one of the best-documented reference implementations available to read
✗ Cons
- •It has been acquired by Cursor. continue.dev is now a farewell page, not a product site — that is the single most important fact about it in 2026
- •There is no published pricing to review because there is no longer a commercial product being sold at that address
- •Acquisitions of open-source projects usually mean maintainer attention moves to the acquirer's roadmap, whatever the repo's commit graph looks like this week
- •941 open issues is a large backlog to inherit if upstream maintenance slows
- •The hosted account layer, subscriptions and any team features are the parts most at risk — code survives acquisitions, services often do not
- •Adopting it new in 2026 means betting on either upstream continuing or your own team picking up maintenance; those are very different commitments
- •Bring-your-own-model always meant bring-your-own-bill too — you still pay an inference provider on top, so 'free and open source' was never the whole cost
- •Self-hosting the full stack is real operational work, and it is work you now do without a vendor to escalate to
Continue Pricing 2026
There is no pricing page left to quote — that path closed with the acquisition. What follows is the honest replacement: what you can still get, what you can no longer buy, and what running this will actually cost you.
Open source
- •Apache-2.0 licence
- •35,607 stars, 5,279 forks
- •Not archived, still receiving commits
- •VS Code and JetBrains
- •You supply the model and the bill
Teams that can maintain their own fork
Hosted product
- •continue.dev is an acquisition notice
- •No pricing page to quote
- •Subscription questions answered in a site FAQ
- •Acquired by Cursor
- •Not a plan you can sign up for
Nobody — this path has closed
The real cost
- •Model API spend, or
- •Local GPU to run open weights
- •Engineering time to maintain a fork
- •No vendor support escalation
- •Migration cost if you leave later
Anyone budgeting this honestly
Continue vs Cline vs Cursor
| Feature | Continue | Cline | Cursor |
|---|---|---|---|
| Status in 2026 | ⚠️ Acquired by Cursor | ✅ Actively developed | ✅ Actively developed |
| Licence | ✅ Apache-2.0 | ✅ Open source | ❌ Proprietary |
| Bring your own model | ✅ Any LLM, local or hosted | ✅ Any LLM | ⚠️ Vendor-managed |
| Editor support | ✅ VS Code and JetBrains | ⚠️ VS Code focused | ❌ Own editor |
| Self-hosting | ✅ Full stack | ✅ Runs locally | ❌ Cloud service |
| Vendor support | ❌ None going forward | ⚠️ Community | ✅ Commercial |
| Published pricing | ❌ Product discontinued | ✅ Free, pay inference | ✅ Published tiers |
| Best fit | Teams forking and maintaining it themselves | BYO-model users who want an active project | Teams who want a supported product |
If You Are Moving Off Continue
Start by working out which property you were actually buying, because the right destination differs entirely depending on the answer. If it was open source and bring-your-own-model, Cline and Aider are the closest actively developed equivalents, with Roo Code a reasonable third.
If it was JetBrains coverage — the thing most rivals skip — GitHub Copilot and Tabnine both ship real JetBrains plugins rather than an afterthought. If it was the agentic editing experience and self-hosting was never the requirement, Cursor is where the team went, which makes it the path of least resistance.
One practical note on migration: your model configuration is the portable part. Every bring-your-own-model tool wants the same three things — a provider endpoint, a key, and a model name. Rules files and custom prompts move over with light editing. What does not move is anything wired to Continue's hosted accounts, so inventory that before you set a cutover date.
Frequently Asked Questions
Is Continue still available in 2026?
The code is; the product is not. continue.dev now serves a notice that Continue was acquired by Cursor, alongside a short FAQ covering whether the open source is still available, what happened to user data, and what happens to subscriptions. The GitHub repository continuedev/continue remains public, Apache-2.0 licensed, and not archived — it showed 35,607 stars, 5,279 forks and commits landing on the day of this review.
What happened to Continue?
It was acquired by Cursor. The company's own statement frames the mission as ensuring developers are amplified rather than automated, and says that commitment carries on in the work ahead, while thanking the community for helping build a pioneering open-source coding agent. It explicitly notes the open-source codebase remains freely available as a foundation for others — which is the practical takeaway for anyone currently depending on it.
What did Continue actually do?
It was an open-source AI code assistant for VS Code and JetBrains, built around bring-your-own-model. You pointed it at any LLM — a hosted API, or open weights running locally through something like Ollama — and got autocomplete, chat, and refactoring inside your existing editor. The pitch was straightforward: the ergonomics of a commercial coding assistant without sending your codebase to a vendor you did not choose.
Should I still adopt Continue?
Only with your eyes open. Adopting it new in 2026 means accepting that upstream direction is uncertain and that you may end up maintaining your own fork. That is a real and defensible choice for a team with a hard self-hosting requirement and the engineering capacity to back it. For everyone else, an actively developed project is a lower-risk starting point. If you already run Continue in production, nothing breaks today — but plan the fork or the migration deliberately rather than by surprise.
What are the best Continue alternatives?
It depends which property you were buying. If it was bring-your-own-model and open source, Cline and Aider are the closest active equivalents, and Roo Code is worth a look. If it was JetBrains coverage, GitHub Copilot and Tabnine both ship first-class JetBrains plugins. If it was the agentic editing experience and you no longer need self-hosting, Cursor — the acquirer — is the obvious destination, which is presumably part of the point.
Was Continue free?
The open-source assistant was free under Apache-2.0, but 'free' never meant zero cost. Bring-your-own-model means you pay an inference provider per token, or you buy and run the hardware to serve open weights yourself. There was also a hosted layer with accounts and subscriptions, which is exactly what the site FAQ now addresses post-acquisition. Budget the inference and the maintenance, not the licence.
ChatGPT already recommends Continue. Does it recommend yours?
If you're building in AI coding assistants, run a free AI-visibility scan on your own product — we ask ChatGPT across 5 prompt angles and score how often you get named. ~30 seconds, no signup, no card.
Where Continue Users Are Going Next
Three actively developed coding agents, reviewed on pricing, model support and editor coverage.
Affiliate disclosure: Some links on this page are affiliate links. If you sign up through them, AISO Tools may earn a commission at no extra cost to you. This never affects our rankings or reviews.
📬 Get the best new AI tools delivered weekly
One concise email with fresh launches, trending picks, and featured standouts.
Join thousands of professionals who discover the best AI tools every week. No spam — unsubscribe anytime.