Roo Code's GitHub repository was archived on May 15, 2026. The archived project says the extension was shut down and points readers to Cline and Zoo Code; the former Roo team moved on to Roomote. Kilo Code is another option with a separate, detailed Roo migration guide. These routes are not interchangeable: one is a continuation, another has an explicit settings import, and Kilo documents file-by-file configuration changes.

First protect the work, then choose the tool. A settings import can move rules or provider configuration; it does not prove that your current diff, failed attempts, decisions, or unfinished task were carried over.

Choose by the migration you actually need.

Cline: the alternative named by Roo.

Roo's archived repository lists Cline as an alternative and notes that Roo originated from it. Treat Cline as a fresh destination unless its current documentation confirms a specific import path for the settings you use. Recheck rules, MCP servers, provider credentials, and model selection instead of assuming the old setup came across.

Read Cline's current documentation.

Zoo Code: a community continuation with a settings importer.

Roo's archived repository also links Zoo Code, a community fork. Zoo Code documents a concrete two-step settings migration: export a settings file in Roo, then import that file in Zoo Code. Its documentation warns that the export may contain sensitive settings, including API keys. Store it securely and do not share it. Verify the imported providers, rules, and MCP connections before continuing work.

Follow Zoo Code's Roo-to-Zoo settings migration.

Kilo Code: a separate, documented migration route.

Kilo publishes mappings for Roo project rules, custom modes, and MCP settings, and explains which features and provider credentials need extra attention. Its current extension has changed from the older Roo-derived codebase, so follow the guide for the version you install and verify each migrated item. Roo's repository does not list Kilo as its own recommendation; this is Kilo's migration path.

Read Kilo's Roo migration guide.

Roomote: the former Roo team's cloud direction.

Roomote is the former Roo team's next product, not simply another local IDE extension. Check its current workflow, data handling, and hosting model if you are considering it; do not assume your local extension setup or unfinished chat transfers automatically.

Visit Roomote.

What the "3 million" figure does and doesn't mean.

Roo's sunset notice reported more than three million extension downloads. Downloads are a cumulative install measure, not a count of active users today or of people who still need to migrate. Use the number as context for Roo's reach, not as proof that three million people are currently searching for a replacement.

Protect an unfinished project before switching.

  1. Inspect the repository. Record git status --short, git diff --stat, the current branch, and the last test or check that passed.
  2. Back up tracked changes if needed. git diff --binary captures tracked edits, but not untracked or ignored files. List untracked files with git ls-files --others --exclude-standard and copy the important ones separately. Review backups for secrets before sharing them.
  3. Save the task state. Write down the goal, files changed, decisions, failed attempts, exact error, verified checks, and next action. Keep the old Roo task available until the new tool has passed a real test.
  4. Move configuration deliberately. Review project rules, custom modes, MCP servers, provider settings, and keybindings. Use the destination's documented import or conversion; re-authenticate when required.
  5. Verify before uninstalling. Open the same repository in the new tool, check the loaded rules and integrations, ask for a read-only summary of the working tree, then try one bounded edit on a branch and run the relevant tests.

Do not let Roo and the new agent edit the same working tree concurrently. Keep a rollback copy until the destination has completed a representative task and its diff is understood.

What ShardStitch can carry across.

ShardStitch does not convert Roo settings or guarantee a full conversation import. It can prepare a continuation packet from project state available locally: Git changes, changed files, saved notes or captured session context, failed attempts, verification state, and next action. Any old conversation detail is available only if it was captured or saved before the Roo session was lost. Review the packet before handing it to Cline or Kilo Code, both supported handoff targets. Zoo Code is a community fork you can install and configure yourself; ShardStitch has no Zoo Code adapter.

Sources and verification

Related recovery guides