Roo Code and Continue have both ended, so "Roo Code vs Continue" is no longer a choice between two products — it is a question of which one's setup survives and where it goes. Roo Code was shut down on May 15, 2026, and its settings can be exported and imported into Zoo Code, a maintained continuation. Continue was acquired by Cursor and frozen in June 2026; its local config file still works with any OpenAI-compatible endpoint, while everything it hosted is gone. Checked October 1, 2026.
For each tool's own exit — Roo against Cline, Continue against its alternatives — see Roo Code vs Cline and Continue alternatives. This page is for the reader who has one or both installed and wants to know what each leaves behind.
Where each one stands
| Roo Code | Continue | |
|---|---|---|
| What happened | The README says the Roo Code extension was shut down on May 15, 2026, and the repository is archived | continue.dev says it was acquired by Cursor; the README says the repository is read-only and no longer actively maintained |
| Last builds | 3.54.0, May 15, 2026 — still served by the VS Code Marketplace | VS Code extension 2.1.0 (June 19, 2026), CLI 1.5.47 on npm (June 18, 2026) |
| What the old domain does | roocode.com redirects to Roomote, the team's new paid product, from $49 a month | A farewell page; the Hub no longer resolves |
| Where your setup lives | In the extension's settings, exportable to a file from the settings panel | In ~/.continue/config.yaml, a file you already own — plus anything you kept on the Hub, which is gone |
| Maintained continuation | Zoo Code: Apache-2.0, former Roo contributors, v3.84.0 on GitHub (September 26) and 3.85.x on the Marketplace (September 30), with a documented Roo import | None from the same team; Cursor is a different, proprietary editor |
The asymmetry that decides it
The two exits break in opposite places. Continue's local half survives and its hosted half is dead. A model entry on provider: openai with an apiBase in config.yaml needs nothing from Continue's servers, so the frozen extension and CLI keep working against any OpenAI-compatible endpoint; what does not survive is anything that lived on the Hub, which has to be rewritten as local config. Roo's product is dead but its settings travel. The extension will not be updated, but its settings export to a file, and Zoo Code imports that file into a maintained fork of the same codebase.
So the lowest-effort path is different for each. A Roo user can be on a maintained tool in two clicks. A Continue user can keep working today without moving at all — at the cost of running software that will not get fixes, new model ids or security updates — and has no importer to a maintained agent when they do move.
What to do, by situation
| You are on | Lowest effort | What it costs you |
|---|---|---|
| Roo Code | Export settings, install Zoo Code, import the file | Trust in a new maintainer team; the exported file can contain API keys |
| Roo Code, and you want a larger project | Cline or Kilo Code, re-entering providers and rules by hand | An afternoon of setup; Roo's modes and prompts do not carry over automatically |
| Continue, with a local config.yaml | Keep running the frozen build while you plan a move | No fixes or new model ids; any Hub-based configuration must be rewritten locally |
| Continue, moving now | Cline or opencode — see Continue vs Cline | Rewriting config.yaml in the new tool's format; there is no importer |
| Both installed | Consolidate on one maintained agent | Two frozen extensions in one editor is two unpatched attack surfaces |
Models and what they cost now
Both tools were bring-your-own-key, so the model bill never depended on either company and still does not. Two things change when a client is frozen. Its built-in model list stops moving, so new model ids have to be typed by hand; and any per-token prices it shows are the ones you entered, not what your provider charges. If you point either at an OpenAI-compatible gateway, rates are the gateway's: on Kunavo, Claude Sonnet 5 lists $1.40 per million input tokens and $7.00 per million output, and Claude Haiku 4.5 $0.70 and $3.50, billed per token from a prepaid balance with a $10 minimum top-up. Setup for the endpoint side is on Continue and Roo Code; Zoo Code's settings keep the same Base URL field for its OpenAI-compatible provider. Nobody at Kunavo has run any of the three against its endpoint.
If you are choosing a maintained agent rather than salvaging a setup, the AI agent API directory lists which current clients take a custom endpoint, on which protocol, and which are archived.
FAQ
Are Roo Code and Continue still maintained?
No. Roo Code's repository was archived on May 15, 2026 and its README states the extension was shut down that day; the last release is 3.54.0, which the VS Code Marketplace still serves. Continue's README says the repository is no longer actively maintained and is read-only, continue.dev says Continue was acquired by Cursor, and its last builds are VS Code extension 2.1.0 (June 19, 2026) and CLI 1.5.47 on npm (June 18, 2026). Both still install and run; neither will receive fixes. Checked October 1, 2026.
Can I move my Roo Code settings somewhere else?
Yes, and more easily than for Continue's hosted parts. Roo Code has an Export button in its settings that saves a settings file, and Zoo Code — an Apache-2.0 continuation run by former Roo contributors — documents importing that file with its Import Settings button, merging it into the current setup. The exported file can contain API keys, so store it carefully. Moving to Cline or another agent instead means re-entering providers, prompts and rules by hand.
What still works in Continue after the shutdown?
The local half. A ~/.continue/config.yaml with a model on provider: openai and an apiBase still points the VS Code extension and the CLI at any OpenAI-compatible endpoint, because nothing in that path needs Continue's servers. The hosted half is gone: Hub configurations and the Continue account no longer resolve, so anything you set up through the Hub has to be rewritten as a local config file. No new model ids or fixes will arrive.
Should I switch from Roo Code to Continue, or the other way round?
Neither, as a destination. Both are frozen, so moving from one to the other trades one unmaintained tool for another. If you are on Roo Code, the smallest move is Zoo Code, which imports Roo's exported settings. If you are on Continue and depend on its config file and CLI, you can keep running the frozen build while you plan a move to a maintained agent such as Cline or opencode; Continue's config.yaml does not import into either.
Can Roo Code, Zoo Code or Continue use Kunavo?
They can be pointed at it the same way as any OpenAI-compatible endpoint: Continue through provider: openai with apiBase https://api.kunavo.com/v1 in config.yaml, and Roo Code through its OpenAI Compatible provider with the same base URL; Zoo Code's settings keep a Base URL field for that provider. Kunavo has setup pages for Continue and Roo Code written from their documentation, and has not run any of the three against its endpoint, so treat the first request as your own test.
Checked October 1, 2026: the GitHub API for RooCodeInc/Roo-Code (archived, release 3.54.0), continuedev/continue (README, releases) and Zoo-Code-Org/Zoo-Code (licence, releases, README); the VS Code Marketplace API for the three extensions' current versions; npm for @continuedev/cli; Zoo's Roo-to-Zoo migration guide; and roocode.com's redirect to roomote.dev. None of the three extensions was installed here. Kunavo token rates come from the live catalog.