Is Continue Still Free? What It Costs After the Cursor Acquisition
There is no subscription left to buy: Continue was acquired by Cursor in June 2026, the pricing page returns a 404, and the Hub tiers that used to cost $3 per million tokens or $20 per seat are gone. What remains is the Apache-2.0 extension — still free, still installable, still BYOK. Your only recurring cost is the model you point it at.
AICoding score
Quick Verdict
7.0 / 10 — still the most flexible free assistant, but no longer a safe long-term bet.
The money question is settled: <strong>there is nothing left to pay Continue itself</strong>, so your bill equals your model provider bill — near zero on local models, $20-40/month if you push frontier models. The open question is not cost but drift: <strong>the project froze after the acquisition</strong>, so you are pinning a finished version while your editor and your model providers keep moving.
Use Continue if…
- You want a free, auditable BYOK assistant and already pay for model access
- You need fully local or air-gapped inference (Ollama / LM Studio)
- You want one assistant across VS Code, JetBrains and Neovim
- You are comfortable pinning a frozen version you have audited once
Skip it if…
- You need the tool to track new models and editor releases (→ Cline)
- You need team governance, shared configs or SSO (the Hub is gone)
- You are standardising for a team that will not accept an unmaintained dependency
- You want a managed agentic experience rather than configuration (→ Cursor)
Core Features
The Acquisition Is The Story
In June 2026 Cursor acquired Continue. The homepage now reads 'Continue (acquired by Cursor)', the open-source codebase stays freely available, and the commercial layer — the Hub — disappeared along with its pricing page. Whatever Continue used to be worth to you, that single event is what should drive the decision to stay or move.
BYOK Is Now The Entire Cost Model
With no subscription left to buy, your bill is exactly your provider bill: near zero on a small local model, a few dollars a month on a budget cloud model, $20-40+ on frontier models driven agentically. That is unusually honest economics — and also the reason the tool is worth keeping if you already pay for model access elsewhere.
The Free Floor Never Expires
Apache-2.0 means the code you have is yours to run, fork and audit. Point it at Ollama and the marginal cost is electricity; vendors cannot raise the price, meter you, or shut the door. Very few assistants in this category can promise that, and none of the managed ones can.
What Disappeared With The Hub
The hosted layer used to handle shared configuration, team governance, analytics and SSO for $20 per seat. It is no longer sold, and there is no like-for-like replacement — so a team that relied on it now owns that work: versioned configs in a repo, an internal fork, or a different tool altogether. Free can be more expensive than it looks.
Maintenance Is The Real Trade
The trade is no longer price, it is drift. 2026 write-ups report the repository is effectively frozen, which means no new model support, no editor-release fixes and no security patches. For a pinned local setup that may be acceptable; for a team standard, it is a dependency risk you should date-stamp and revisit rather than assume away.
Pricing
The only tier that exists today: self-hosted, config-driven, Apache-2.0. Connect a local model for a genuine $0 recurring cost, or your own cloud key and pay that provider at their rates.
- $0, no account needed
- Any model (BYOK)
- Local Ollama / LM Studio
- VS Code · JetBrains · Neovim
Formerly the pay-as-you-go hosted tier — and before March 2026 it was a free Solo plan. It charged $3 per million tokens (input plus output) with no monthly fee, and stopped being sold after the acquisition.
- $3 / M tokens (input + output)
- No monthly fee
- Managed agents in the Hub
- No longer sold
The team tier that added shared private agents, governance and SSO, with $10 of model credit bundled into each seat. Gone with the Hub — and with it the only native way to standardise configurations across a team.
- $10 model credit per seat
- Shared agents + governance
- Gmail / GitHub SSO
- No longer sold
The sales-led tier: SAML/OIDC SSO, BYOK at organisational scale, committed usage, invoicing and an SLA. Enterprises that depended on it are the ones most affected by the acquisition.
- SAML / OIDC SSO
- Org-wide BYOK
- Committed usage + SLA
- No longer sold
* Verified September 13, 2026: continue.dev/pricing returns a 404 and the homepage carries the acquisition notice, so the Hub figures above are historical rather than purchasable. The Apache-2.0 extension remains free. Reports that the repository was frozen after the acquisition come from 2026 third-party write-ups — confirm the current state on the official site and repository before making a team-level decision.
What Continue Really Costs Now
| Task / Plan | Usage | Typical cost | What to watch |
|---|---|---|---|
| The extension itself | VS Code / JetBrains / Neovim plugin | $0 — and no one can change that | Apache-2.0: the copy you have keeps working |
| Local model setup | Ollama chat, completion and embeddings | $0 recurring | The genuine zero-cost configuration |
| Cloud BYOK, light use | Budget model for completion, occasional chat | $1-5/mo at provider rates | No markup, no intermediary, no seat fee |
| Cloud BYOK, heavy use | Frontier models on agentic tasks | $20-40+/mo | Now that nothing is metered, your provider bill is the entire cost |
| Hub Starter (historical) | Pay-as-you-go hosted agents | Was $3 per million tokens | No longer sold after the acquisition |
| Hub Team (historical) | Shared agents, governance, SSO | Was $20/seat including $10 credit | A 5-person team with moderate agent use ran about $250/mo |
| Team collaboration now | Sharing configs and rules across developers | DIY — engineering hours | Versioned configs in a repo, or an internal fork |
| Maintenance drift | New models, editor releases, security fixes | Unpriced risk | The cost of free here is paid in staleness, not invoices |
Verified September 13, 2026. Continue was acquired by Cursor in June 2026; the pricing page returns a 404 and the Hub tiers are historical. The Apache-2.0 extension remains free to self-host with your own model.
Continue Deals & Ways to Pay Less
There are no discounts to chase here — the two real levers are running a local model for a $0 floor, and using keys you already pay for instead of opening a new subscription.
Continue vs The Field
Continue vs Cline
The closest replacement — same $0 model, still shippingCline is Apache-2.0, free, BYOK and runs in both VS Code and JetBrains, which is almost exactly what Continue offered — except Cline is actively developed. If your reason for leaving is maintenance drift, Cline is the like-for-like migration and costs the same $0. Continue wins only if you are on Neovim or want its config-driven, assistant-style interaction rather than an autonomous agent.
Cline — same cost, active developmentContinue vs GitHub Copilot
$10-19 per seat buys maintenance and zero configurationCopilot is the opposite trade: you pay $10/month individually or around $19 per seat commercially, and in return you get a maintained product, cross-editor reach, IP indemnification and no config file to write. Against Continue's $0 that is a real increase — but it is the price of not owning the maintenance problem yourself.
Copilot for maintained zero-setup · Continue for $0 + controlContinue vs Cursor
The acquirer — $20/month for the agentic experienceCursor acquired Continue, and its $20/month editor is the reason: an opinionated, polished agentic IDE rather than a configurable assistant you assemble. Migrating from Continue to Cursor is not a like-for-like move so much as a change of philosophy — and for teams already paying for model keys, it means paying for the same intelligence twice.
Cursor for managed agent · Continue for BYOK cost controlContinue vs Sourcegraph Cody
Free BYOK vs enterprise codebase retrievalCody is built for large multi-repo codebases with enterprise compliance (SOC 2 Type II, on-prem options) and is priced accordingly. Continue wins on local/offline operation, model freedom and a $0 floor; Cody wins on retrieval quality at scale and on being a vendor with a support commitment — which is precisely what the acquisition removed from Continue.
Cody for enterprise scale · Continue for local + $0Who Continue Is Best For
Privacy-first and air-gapped work
Run everything against a local model so no code leaves the machine, with no vendor able to meter or interrupt it.
Developers already paying for model access
If you hold Anthropic, OpenAI or Gemini credits, Continue turns them into an assistant without a second subscription on top.
Free assistance inside JetBrains
One of the few free assistants with genuine JetBrains parity, which is why it survives in shops that will not switch editors.
Teams that relied on shared AI configuration
The Hub handled shared prompts and governance at $20 per seat; with it gone, this use case now means rolling your own versioned configs — or choosing a tool that still sells the feature.
Long-lived projects that need to keep up
If new models, editor releases and security patches matter, a frozen dependency is a growing liability regardless of how good the licence is.
How to Pay the Least for It
Install the extension and point it at your own model
The marketplaces still serve the extension, and configuration still works as documented. Declare a local model for autocomplete and, if you want it, a cloud model for chat and edits — the whole setup is one file you can version-control.
Decide your model tier before your first busy month
Because there is no subscription, the only thing that can surprise you is token spend. Local models make the floor $0; a budget cloud model keeps it in single-digit dollars; pushing frontier models agentically is what turns a free tool into a $20-40/month habit.
Set a migration review date rather than debating it now
The setup is cheap enough that you do not have to decide today — but it is also frozen, so pick a date (a quarter out is reasonable) to re-check whether the repository is still static and whether your team needs the governance the Hub used to sell.
FAQ
Is Continue still free in 2026?
The extension is free, and it is the only thing left that is. Continue was acquired by Cursor in June 2026, the pricing page now returns a 404, and the Hub tiers that used to be sold — Starter at $3 per million tokens, Team at $20 per seat — are no longer available. The Apache-2.0 extension itself still installs, still connects to your own model, and still costs nothing.
What actually happened to Continue?
Cursor acquired Continue in June 2026. The company's homepage now reads 'Continue (acquired by Cursor)' and states the open-source codebase remains freely available as a foundation for others. What disappeared is the commercial layer: the hosted Hub, its pricing page, and the team governance features. Several 2026 write-ups report the GitHub repository has gone read-only with development frozen, so treat the extension as a finished artifact rather than a maintained product.
What does Continue cost me now?
Your model bill and nothing else. There is no subscription to buy any more, so the only recurring cost is whatever the provider you connect charges — roughly $0 if you run a local Ollama model, a few dollars a month on a budget cloud model, or $20-40+ if you push frontier models through agent-style workloads. Use it with a local model and the marginal cost is effectively your electricity.
What were the old Continue Hub prices?
For reference, since they are gone: Starter was $3 per million tokens (input and output combined, no monthly fee) and had replaced a free Solo tier in March 2026; Team was $20 per seat per month including $10 of model credit per seat; Company was custom-quoted with SAML/OIDC SSO, BYOK and an SLA. A five-person team on Team with moderate agent usage ran about $250/month — $100 of seats plus roughly $150 of token overage — compared with about $180/month on pure Starter without the governance features.
Can I run Continue fully offline with local models?
Yes, and this is the part the acquisition did not change. Continue declares models in a config file, so you can point it at Ollama or LM Studio and run autocomplete, chat and @codebase retrieval with no cloud calls at all. For proprietary, healthcare or air-gapped code this remains one of the strongest privacy postures of any mainstream assistant — and it is the configuration with a genuine $0 recurring cost.
Is Continue still maintained?
Reports through 2026 say no: the project has been frozen rather than abandoned mid-version, so the code works but new models, IDE changes and security fixes are not being merged. That is the real cost of staying — not money, but drift. Your editor keeps updating, your providers keep shipping new models, and the assistant does not follow. Set a review date rather than assuming it will keep working indefinitely.
Is Continue safe for proprietary code?
The privacy posture is sound — it is Apache-2.0 and auditable, and a fully local configuration sends nothing anywhere. The risk that changed in 2026 is not data handling but maintenance: unpatched dependencies and an unmaintained extension are a different kind of exposure than an unmaintained cloud service. Audit the frozen version once, then decide how long you are comfortable pinning it.
Does Continue work in JetBrains IDEs?
Yes — VS Code, JetBrains and Neovim, with genuine feature parity rather than a reduced JetBrains build. Since the extension still installs from the marketplaces, this remains its practical advantage over tools that are editor-specific. It is also why some teams keep using it after the acquisition: it is the cheapest way to give an existing JetBrains shop an assistant without changing editors or buying seats.
What does bring your own model (BYOK) mean in Continue?
It means Continue ships no model of its own. You declare providers and models in config.yaml — local Ollama, or cloud keys for OpenAI, Anthropic, Gemini, xAI or any OpenAI-compatible endpoint — and assign them roles: a small fast model for tab completion, a frontier model for chat and edits, an embedding model for @codebase. You are billed by those providers directly, with no markup and no intermediary. Now that the Hub is gone, BYOK is effectively the entire product.
What are the best alternatives to Continue now?
Cline is the closest like-for-like replacement — free, Apache-2.0, BYOK, and actively developed in both VS Code and JetBrains, which is exactly where Continue is drifting. GitHub Copilot at $10-19 per seat buys you active maintenance, cross-editor reach and team controls without any configuration. Cody is the enterprise option if you need codebase-scale retrieval and SOC 2. And Cursor — now Continue's owner — is the paid path if you want the agentic experience the acquisition was really about.
Is there still a paid Continue plan I can buy?
No. The pricing page returns a 404, the Hub tiers are no longer sold, and the homepage carries an acquisition notice instead of a price list. The only money that leaves your account when you use Continue today goes to whichever model provider you connect — which also means there is no way to buy support, an SLA or team governance from Continue any more, no matter what you are willing to pay.
Should I keep using Continue or migrate?
Keep using it if your setup is local-model or simple BYOK, your cost is already near zero, and you are comfortable pinning a frozen version. Migrate if any of three things is true: you need team governance and shared configuration (the Hub is gone), you need the extension to track new models and editor releases, or you are standardising for a team that will not accept an unmaintained dependency. In practice the migration cost is mostly re-writing a config file, which is the main reason this decision is easy to defer but should not be forgotten.