Continue Sospendi
Overview
Continue is an open source IDE extension and CLI for custom models, rules, and autocomplete/chat workflows across VS Code and JetBrains (Continue).
In June 2026 Continue was acquired by Cursor; the product is no longer developed and the open-source code base remains available under Apache 2.0 (Continue, GitHub, The New Stack). The final releases (VS Code extension 2.x and CLI) removed anonymous telemetry and authentication, and the hosted Hub and sign-in flow were retired.
The original case for Continue, model choice and self-hosted endpoints with a lighter footprint than full agent platforms, still describes what the last release does, but it now comes without a maintainer. Continue is therefore rated Hold.
Adoption Signals
- The continue.dev homepage now reads "Continue has joined Cursor" and states that the company was acquired by Cursor, with the open-source code base remaining "freely available as a foundation for others" (Continue).
- The repository README states that
continuedev/continue"is no longer actively maintained and is read-only for all users" and describes a "Final 2.0.0 Release"; it recommends the Continue CLI over the JetBrains plugin (GitHub README). - The last extension releases, v2.0.0 and v2.1.0 for VS Code, were published on 19 June 2026 (GitHub releases); commits in July 2026 only touched the documentation site, including removing the sign-in link after the login flow was retired (Commit history).
- At the time of the acquisition the repository had about 34,300 GitHub stars and 4,800 forks (The New Stack); by September 2026 it had about 36,000 stars and 5,400 forks (GitHub), and the VS Code extension about 4.25 million installs (VS Code Marketplace).
- The New Stack reported on 22 June 2026 that the deal was an acqui-hire and that Continue's homepage FAQ gave existing users until 15 July 2026 to export their data before deletion, with recurring billing disabled (The New Stack); a contributor issue asks for the repository to be formally archived (Issue #12629).
Risks
- Unmaintained code with repository access. The extension reads workspace files and sends them to model endpoints; without upstream security fixes, vulnerabilities in it or its dependencies will not be patched unless the organisation maintains a fork.
- Configuration that depends on retired services. Setups that referenced Hub assistants, shared blocks or Continue sign-in no longer work; the final CLI switched its default configuration to explicit model definitions instead of Hub slugs (Commit history).
- IDE and model drift. New VS Code and JetBrains versions, and new model APIs, will gradually break compatibility, and the JetBrains plugin was already the less recommended surface before the shutdown (GitHub README).
- Data already in the vendor cloud. Teams that stored assistants, configurations or history on Continue's hosted service needed to export before the announced deletion date and should confirm deletion for their own records (The New Stack).
Pros & Cons
Advantages
- The final 2.x release removed anonymous telemetry and mandatory authentication, so the extension now runs as a purely local client against whatever model endpoints the organisation configures, including self-hosted ones.
- The full code base (VS Code extension, JetBrains plugin and CLI) remains available under Apache 2.0, so an organisation can fork and maintain it internally without licence risk.
- It reached real scale: about 36,000 GitHub stars and more than 4.2 million VS Code Marketplace installs in September 2026, so many teams already have working configurations, rules and prompts to migrate from.
Disadvantages
- The product is discontinued: Continue was acquired by Cursor in June 2026, the repository is marked as no longer actively maintained and read-only, and the 2.x releases of 19 June 2026 are declared final.
- Hosted parts are gone: the sign-in flow was retired, the default configuration no longer references Hub slugs, hub.continue.dev no longer resolves, and cloud data was due for deletion after 15 July 2026.
- No further security fixes, model updates or IDE compatibility fixes will ship upstream, so any continued use means owning an unmaintained IDE extension that reads source code and calls external model APIs.
Recommendation
Hold Continue for new adoption: do not start new trials or roll it out to additional teams. Where it is already in use, treat the remaining time as a migration window. Keep the final 2.x release pinned, point it only at approved model endpoints, remove any dependency on Hub or sign-in, and move rules and prompts into files kept in the repository so that they can be reused with another tool.
Choose the replacement by the reason Continue was selected. For a supported IDE assistant, GitHub Copilot, Cursor and Tabnine Enterprise are rated Adopt; Copilot's bring-your-own-key option covers model choice, including local models (Copilot BYOK), and Tabnine Enterprise suits teams that need self-hosted deployment. Where an open-source agent with self-hosted or EU-hosted models is the requirement, Goose and OpenHands are rated Trial and OpenCode is on the radar at Assess. Forking Continue is only reasonable for organisations prepared to own security patching and IDE compatibility for an extension that has access to their source code.
Sources
Consulenza
Dal radar all'implementazione
Avete valutato le tecnologie — vi aiutiamo a portarle nei sistemi produttivi in modo sicuro e misurabile.
