Continue−9 Mixed

GILD Review

GILD's call and the buying facts behind it.

From GILD research

Should we adopt Continue?

What happens to your team's Continue setup now that Cursor owns it?

30-Second TakeKeep Continue only as a bridge, because Cursor acquired it in June 2026 and left the repository read-only.
Best fitTeams already running Continue on local or company-hosted models, for the months before they switch.GILD Review
Consider another workflowIf you need vendor support, admin policy, or support for new models, a maintained tool such as Cline or GitHub Copilot fits better.GILD Review

Drawn from 112 sources and 1 operator insight

GILD analysis

Continue Review

Treat Continue as a bridge to a maintained tool, because maintenance and the hosted service ended in June 2026 and a team that keeps it owns every fix and model change. Its final Apache 2.0 release still runs in VS Code, JetBrains IDEs and the terminal with no Continue account. Keep it during a move only if code must stay on models you host.

AI Developer Assistant
Governance

The decision

Best fit: Teams already running Continue on local or company-hosted models, for the months before they switch.
Consider another workflow: If you need vendor support, admin policy, or support for new models, a maintained tool such as Cline or GitHub Copilot fits better.
Adoption condition: Start no new rollouts. Pin the final release. Share one config.yaml and the approved model endpoints. Set a date for the move.

Basis: Continue's own pages, repository and marketplace listings, plus its GitHub forks and issue tracker. In a pilot, compare accepted autocomplete suggestions on Continue and its successor.

Buying & deployment factsWhat engineering leaders should verify before a broader rollout.

How you buy it

Free, Apache 2.0

Paid plans ended with the Cursor acquisition, and unused credits are refunded.

Source 1, Continue Dev, Inc., Continue (acquired by Cursor): Continue (acquired by Cursor)Source 5, continue.dev, continue.dev FAQ (site script): continue.dev FAQ (site script)Source 2, Continue Dev, Inc., Continue on GitHub: Continue on GitHub

Details

You no longer buy it. Paid plans ended when Cursor acquired Continue: recurring billing is disabled and unused paid credits are refunded. The extension, plugin, and CLI stay free under Apache 2.0.

Cost drivers

Model usage only

You pay your provider or run local models. Continue charges nothing and has no seats.

Source 3, Continue Dev, Inc., Continue on the Visual Studio Marketplace: Continue on the Visual Studio Marketplace Source 4, Continue Dev, Inc., config.yaml reference: config.yaml reference

Details

Model usage only. You pay your own provider for cloud models or run local models on your own hardware; Continue charges nothing and has no seats.

Where it runs

VS Code, JetBrains, CLI

Extension 2.0.0, plugin 1.0.67, and the cn CLI, configured from one local file.

Source 6, Continue Dev, Inc., Continue releases on GitHub: Continue releases on GitHub Source 7, open-vsx.org, Open VSX API: Continue: Open VSX API: Continue Source 3, Continue Dev, Inc., Continue on the Visual Studio Marketplace: Continue on the Visual Studio Marketplace Source 8, registry.npmjs.org, npm registry: @continuedev/cli: npm registry: @continuedev/cli Source 4, Continue Dev, Inc., config.yaml reference: config.yaml reference

Details

VS Code extension 2.0.0 on the Marketplace and Open VSX, with a 2.1.0 pre-release build the same day (June 19, 2026), JetBrains plugin 1.0.67 (March 27, 2026), and the cn CLI 1.5.47, each reading config.yaml on the engineer's machine.

What to verify

No maintainer

The repository is read-only and unmaintained, with no admin console, SSO, or central policy.

Source 2, Continue Dev, Inc., Continue on GitHub: Continue on GitHub Source 9, GitHub, SECURITY.md: SECURITY.md Source 10, api.github.com, Pull request #12570: final release cleanup (GitHub API): Pull request #12570: final release cleanup (GitHub API)

Details

The repository is read-only and no longer actively maintained, so plan on no further releases, security fixes included, although SECURITY.md still lists security@continue.dev. The final release removed sign-in, so there is no admin console, SSO, or central policy; governance rests on shared files and your own endpoint management.