What Roo Code Was
Roo Code was a prominent open-source VS Code AI coding agent that forked from Cline and emphasized structured modes, customizable agent behavior, and bring-your-own-model workflows. It became one of the best-known Cline forks because it gave developers more visible control over whether the agent was planning, coding, debugging, or answering questions.
The important 2026 update is that Roo Code is no longer an active product recommendation. The official repository is archived, the Marketplace listing has not moved beyond the May 15, 2026 v3.54.0 release, and the project README says the Roo Code extension was shut down on May 15th. That changes the review from a current buying guide into a historical and migration-oriented reference.
Agent Capabilities and Pricing Model
At its peak, Roo Code offered multi-file editing, terminal command execution, browser/documentation workflows, MCP integration, and explicit human confirmation for risky actions. The mode system was the main differentiator: Code, Architect, Debug, Ask, and custom modes helped constrain the agent’s behavior for different tasks.
The pricing story also changed. The extension itself was free and open source, with users paying for their chosen AI model providers. Optional Roo Code services and paid balances are no longer the adoption path after the May 15 shutdown; new users should treat any remaining marketplace install as unsupported historical software rather than a live SaaS product.
Shutdown, Archive Status, and Migration Paths
The shutdown signals are unusually clear: the GitHub repository is archived, roocode.com redirects to Roomote, and final project activity removed the Roo Code web app and updated the README. This is not merely a stale marketing site; the original team has pivoted away from the IDE extension product.
For teams that still like the Roo workflow, the practical path is migration. Cline is the upstream project and the safest active IDE-agent alternative. ZooCode exists as a community fork for users who specifically want to continue the Roo Code lineage. Roomote is a separate product from the same team, aimed at cloud/Slack-based async engineering work rather than a direct Roo Code extension continuation.
When the Historical Review Still Helps
Roo Code still matters for evaluating the evolution of agentic coding tools. Its custom modes, visible tool permissions, and community-driven iteration influenced how developers think about supervising AI agents inside the editor. It is also useful as a comparison point for Cline, Cursor, Claude Code, and Roomote because it shows the trade-off between local editor control and cloud-based delegation.
However, a discontinued agent should not be selected for new production workflows unless a team knowingly accepts the maintenance risk or uses a maintained fork. Documentation, security updates, marketplace compatibility, and provider integrations can drift quickly in this category, so the lack of official support is a material E-E-A-T and trust concern.
Scores and Trust Signals
Roo Code would have scored much higher as an active open-source VS Code agent in early 2026. After shutdown, the overall score reflects current adoption risk rather than historical influence: strong transparency and open-source history, but weak support continuity and high maintenance uncertainty.
Privacy remains relatively strong for the original BYO-key architecture, but that does not offset the support risk. Developer experience also depends on whether users rely on the archived extension, Cline migration, ZooCode community fork, or Roomote’s separate cloud-agent product. The safest score interpretation is therefore “historically important, currently risky.”
The Bottom Line
Roo Code is best treated as a discontinued but influential Cline fork. It is worth understanding for historical context and migration decisions, but it should not be recommended as a fresh tool choice. New IDE-agent users should start with Cline or a maintained fork; teams interested in the original Roo team’s current direction should evaluate Roomote instead.
