Key findings
- Continue's homepage now states that Cursor acquired the company; recurring billing is disabled, unused paid credits are refunded, and user data has been deleted.
- The repository is read-only and no longer maintained. The last VS Code releases, 2.0.0 and 2.1.0, shipped on June 19, 2026; the JetBrains plugin's last release is 1.0.67 from March 27, 2026.
- The final release removed anonymous telemetry and authentication, so the extension and CLI run on a local config.yaml with no Continue account.
- On October 12, 2026 the VS Code listing showed about 4.3 million installs, Open VSX about 1.68 million downloads, and JetBrains Marketplace about 1.21 million downloads.
- Across 95 public accounts, local models and model choice are the most praised capabilities, reliability is the most frequent concern, and 12 accounts raise the end of maintenance.
- Users report that the last JetBrains plugin fails to load on JetBrains 2026.2 IDEs and on 2026.3 previews. A one-line fix sits in an unmerged pull request.
- Cedra stated in June that it planned a fork, and none has shipped. The most-starred forks of the repository have no commits after June 18.
The final release needs no Continue account: the extension and CLI run from a local config.yaml. A team running it on local models in a closed network can keep the final release for a while, and should set a date to replace it. No maintained community fork had appeared by October 25, 2026.
What changed in June 2026
Continue's homepage now carries one notice: Cursor acquired Continue. Its FAQ says the source code stays available under Apache 2.0, recurring billing is disabled with unused paid credits refunded, and user data has been deleted except where retention is legally required. The data export page at continue.dev/export now returns a 404 error.
The repository README states that continuedev/continue is no longer actively maintained and is read-only for all users. It describes a final 2.0.0 release that removed anonymous telemetry, pulled out authentication, and fixed bugs, and it recommends the Continue CLI over the JetBrains plugin. The only commits after the release move the documentation site.
- June 15, 2026: the acquisition notice appears on continue.dev, and VS Code builds 1.2.24 and 1.3.40 ship.
- June 19, 2026: VS Code extension 2.0.0 and 2.1.0, the last releases.
- July 21, 2026: documentation moved to the root of docs.continue.dev and its sign-in link removed.
What still runs
The VS Code extension, the JetBrains plugin, and the cn CLI still install. They read models, rules, prompts, MCP servers, and data destinations from a local config.yaml. They call whatever provider it names, such as Anthropic, Amazon Bedrock, or Ollama on the same machine, with no Continue account. The hosted service closed. The Continue Hub at hub.continue.dev no longer responds, and paid subscriptions ended.
Nothing upstream will fix a bug, add a model, or answer a security report. One engineer reports chat failing on Ollama responses after the acquisition, and an April 2026 issue reports local models whose tool calls the extension did not register. JetBrains 2026.2 moved the JCEF browser component into its own plugin, and the last plugin release does not declare it, so the Continue tool window no longer loads there. Users have patched and rebuilt the plugin themselves, and the fix in pull request 13186 has no maintainer to merge it.
| Listing | Count | Latest version |
|---|---|---|
| Visual Studio Marketplace | About 4.33 million installs | 2.0.0, plus 2.1.0 pre-release (Jun 19, 2026) |
| Open VSX | About 1.68 million downloads | 2.0.0, plus 2.1.0 pre-release (Jun 19, 2026) |
| JetBrains Marketplace | About 1.21 million downloads | 1.0.67 (Mar 27, 2026) |
| GitHub repository | 36,196 stars, read-only | v2.1.0-vscode tag |
Visual Studio Marketplace, Open VSX, JetBrains Marketplace, and GitHub, read by GILD on October 12, 2026; installs and downloads are cumulative counts as each listing reports them.
What practitioners report
Local and self-hosted models are the most discussed capability, in 31 of the accounts written between January 2025 and September 2026, and 28 of those are positive. All 8 accounts that discuss choosing a model per role praise it. Reliability is raised in all 18 accounts that discuss it, the end of maintenance in 12. Other findings concern setup effort in 10, results that depend on the model in 10, and JetBrains plugin stability in 7. Autocomplete draws the most criticism, and 12 of the 16 accounts that discuss it are critical.
Thirteen accounts speak for a team or an organization, and 8 of them are GitHub issues. They include a company running Continue against its own LLM gateway in the EU and another self-hosting Codestral behind a self-signed certificate. A team preconfigures Amazon Bedrock for users in an air-gapped network. Another account describes IntelliJ freezing three to four times a day across a set of managed Mac and PC endpoints. Helmholtz Blablador made Continue the official way for a couple thousand users to reach its model service. Trail of Bits' AI Handbook approves Continue for client code and bars Cursor from it outside blockchain engagements. A financial services team barred from Copilot tried Continue and chose Tabnine because Continue took more configuring than coding. After the acquisition, one team asked about traceability built on Continue's local data files, and another said it would fork the project.
What it means for a team
A team that runs Continue on local models in a closed network can keep the final release for a while, because it calls no Continue service. The risk grows each month. New models, new IDE versions, and security issues will go unanswered, and the JetBrains plugin has had no release since March 27, 2026.
A team that wants maintained software, admin controls, or vendor support should plan a move. Cline keeps the open-source, bring-your-own-model approach under active development. GitHub Copilot and Cursor sell maintained seats with policy controls and their own model access.
Apache 2.0 allows a fork, and so far nobody has taken one on. Users proposed a community fork days after the acquisition, and Cedra stated on June 23 that it planned one. By August 11, 2026, users were still asking whether anyone maintained a fork. When GILD checked on October 25, 2026, the most-starred forks had no commits after June 18, and Open VSX listed no Continue build newer than 2.1.0. JetBrains users have passed a patched plugin around through a file-sharing link, and one who tried it switched to DevoxxGenie. Red Hat and IBM ran a downstream fork, Granite.Code, for most of 2025 and retired it in October 2025 after sending their fixes upstream, a route that no longer exists.
Methodology
GILD opened Continue's homepage, repository, releases, documentation, and marketplace listings on October 12, 2026 and recorded each figure with that date. The 95 public accounts include Hacker News comments found through its public API and Reddit posts in r/LocalLLaMA, r/ChatGPTCoding, and r/vscode found through the Arctic Shift archive. Others are issues on continuedev/continue and ai4os/ai4os-dev-env found through the GitHub API and two company blog posts. Each was read in full and dated. Counts describe those accounts only. GILD checked the repository's fork list, Open VSX, and the fork and JetBrains issue threads again on October 25, 2026, and added Trail of Bits' account on October 26, 2026.
Products in this piece
Sources
- Official documentation
- 10
- Public source
- 10
- Continue (acquired by Cursor)
- Continue on GitHub (continuedev/continue)
- Continue releases on GitHub
- Continue license (Apache 2.0)
- Continue on the Visual Studio Marketplace
- Continue on Open VSX
- Continue on JetBrains Marketplace
- Continue docs: What is Continue?
- Continue docs: config.yaml reference
- Continue docs: CLI quickstart
- Hacker News submission: Continue has been acquired by Cursor (Jun 15, 2026)
- Red Hat and IBM: Granite.Code, deprecated in favor of Continue (Oct 31, 2025; not a Signals source)
- GitHub issue #12876: impact of the Cursor acquisition on traceability built on Continue's data files (Jun 22, 2026)
- Hacker News, calenti: Continue chat choking on Ollama responses after the acquisition (Jun 17, 2026)
- GitHub issue #12131: Qwen 3.5 and Gemma 4 tool calls not registered (Apr 13, 2026)
- GitHub issue #13185: JetBrains plugin fails to load in 2026.2 IDEs (Aug 24, 2026)
- GitHub issue #12764: Suggestion to make a proper fork (Jun 18, 2026)
- Hacker News, roscas: Continue is no longer updated; alternatives? (Aug 22, 2026)
- Christian Siebmanns, viadee blog: a local AI coding assistant with Continue (Aug 20, 2025)
- GitHub: active forks of continuedev/continue, sorted by stars (read Oct 25, 2026; not a Signals source)