官方到底关停了什么？
Roo Code 官方公告写明：2026 年 5 月 15 日关闭 Roo Code VS Code Extension、Roo Code Cloud 和 Roo Code Router，退还未使用余额，并归档扩展仓库。官方给出的原因是团队不再认为 IDE 是未来方向，后续产品方向转向 Roomote。
这不是“暂时维护放缓”。GitHub 仓库现在是只读状态，最后一个正式扩展版本为 v3.54.0。依赖 Router 或 Cloud 的功能不能通过继续安装旧扩展恢复。
旧扩展还能继续用吗？
What exactly shut down?
The official notice says the VS Code Extension, Roo Code Cloud and Roo Code Router closed on May 15, 2026, unused balances were refunded, and the extension repository was archived. The team said its product direction moved away from IDE-based coding toward Roomote.
This is not a temporary slowdown. The GitHub repository is read-only and v3.54.0 was the final extension release. Router- or Cloud-dependent features cannot be restored by keeping an old extension installed.
Can the old extension still run?
| 部分 / Surface | 当前状态 / Status | 建议 / Recommendation |
|---|---|---|
| VS Code Extension | 仓库归档 / Archived | 仅短期读取旧配置 / Reference old config only |
| Roo Code Cloud | 已关停 / Shut down | 迁移任务与自动化 / Move tasks and automations |
| Roo Code Router | 已关停 / Shut down | 直接配置模型商 / Configure providers directly |
| 本地规则 / Local rules | 可能仍保留 / May remain | 只迁移无密钥配置 / Move secret-free config only |
本地扩展在特定环境下可能仍能运行，但“能启动”不等于“值得继续使用”。归档仓库的安全修复不会持续；官方 Security 页面还保留多项历史公告，涉及命令执行、Auto Approve、MCP、工作区配置和文件边界。
三个替代方向
- Cline：最接近 Roo Code 的开源、模型中立 IDE 路线，也是 Roo Code 官方迁移公告明确推荐的替代品。适合希望保留编辑器内工作流的人。
- OpenCode：如果你愿意把主界面转到终端或桌面端，它的模型选择和产品完成度更强。需要注意权限提示不等于安全沙箱。
- Qwen Code：如果重点是开源、多模型和本地模型路线，可以优先试用；生态和成熟度仍应通过真实仓库验证。
Roomote 是原团队的新方向，但它是云端工程 Agent，不是 Roo Code 扩展的直接替代。迁移前要先确认你需要的是“IDE 内结对编程”，还是“远程异步完成任务”。
安全迁移清单
- 记录正在使用的模型、规则、Modes、MCP 服务器和自动批准范围。
- 只迁移经过审查的规则和提示词，不复制 API Key、令牌或旧云端凭据。
- 在供应商后台撤销 Roo Code Router、Cloud 和不再使用的 MCP 授权。
- 先在测试仓库验证新工具的读写范围、命令批准和失败恢复。
- 确认迁移完成后再卸载旧扩展，并保留不含密钥的配置备份。
来源与更新时间
关停日期、产品范围、退款和官方替代建议来自 Roo Code 官方关停公告；仓库状态和历史风险来自 官方 GitHub 仓库及其 Security 页面。本页更新于 2026 年 10 月 16 日。
The local extension may still run in some environments, but “launches” is not the same as “safe to keep.” Archived code does not receive ongoing security fixes. The official Security page retains advisories involving command execution, Auto Approve, MCP, workspace configuration and file boundaries.
Three replacement paths
- Cline: the closest open, provider-neutral IDE path and the replacement explicitly recommended in Roo Code's own notice. Best for preserving an editor-native workflow.
- OpenCode: a stronger fit if you are ready to move the primary interface to terminal or desktop. Its permission prompts still are not a security sandbox.
- Qwen Code: worth testing when open source, provider choice and local models matter most. Validate ecosystem and maturity on a real repository.
Roomote is the former team's new direction, but it is a cloud engineering agent rather than a drop-in editor extension. Decide whether you need in-editor pairing or remote asynchronous task completion before migrating.
Safe migration checklist
- Inventory models, rules, modes, MCP servers and auto-approval scope.
- Move reviewed rules and prompts only; never copy API keys, tokens or old cloud credentials.
- Revoke Roo Code Router, Cloud and unused MCP authorizations at each provider.
- Test read/write scope, command approval and failure recovery in a disposable repository.
- Uninstall the old extension only after validation, retaining a secret-free configuration backup.
Sources and freshness
Shutdown date, affected products, refunds and the official alternative come from the official Roo Code sunset notice. Repository state and historical risk come from the official GitHub repository and its Security page. Updated October 16, 2026.