Roo Code

Executive Summary

Status: development discontinued May 2026; the team pivoted to Roomote. CEO Matt Rubens announced the shutdown on April 21, 2026; the GitHub repository is archived with a final push on May 15, 2026, and roocode.com now redirects to roomote.dev. The team's new product, Roomote, is a Slack-based operational engineering agent that handles bugs, escalations, and repository questions outside the IDE. Roo Code's official migration recommendation for extension users is Cline.

Roo Code was an open-source AI coding assistant that brought a team of specialized agents directly into VS Code. Originally a fork of Cline, it evolved into a comprehensive platform with role-specific "modes" that constrained agent behavior, plus cloud agents for team collaboration. The project raised $5M in funding and reached roughly 3 million installs and 24,200 GitHub stars at archive time.

---

Product Overview

The following describes Roo Code as it existed at archive time (May 2026).

Roo Code provided AI-powered coding assistance through two complementary surfaces: a free VS Code extension for individual work, and cloud agents for team collaboration. The extension integrated directly into the editor, allowing natural language conversations that could read/write files, execute terminal commands, and automate browser actions.

What distinguished Roo Code from other coding agents was its "modes" system—specialized configurations that constrained what the AI could do. Instead of giving an agent unlimited access, modes like "Architect" (plan without editing), "Debug" (diagnose without refactoring), or "Test" (write tests without changing implementation) kept agents focused and reduced the risk of unintended changes.

Key Capabilities

Product Surfaces

---

Technical Architecture

Roo Code operates as a VS Code extension that spawns agent processes communicating with various LLM providers. The extension has full access to the workspace filesystem, terminal, and can orchestrate browser actions for testing.

┌─────────────────────────────────────────┐
│           VS Code Extension              │
├─────────────────────────────────────────┤
│  Mode System → Tool Access Control       │
│  MCP Servers → Extended Capabilities     │
│  Checkpoints → State Recovery            │
└─────────────────────────────────────────┘
         │                    │
         ▼                    ▼
   ┌──────────┐        ┌──────────────┐
   │ LLM APIs │        │ Cloud Agents │
   └──────────┘        └──────────────┘

Key Technical Details

---

Strengths

• Mode system reduces risk — Role-specific tool access prevents agents from making unintended changes (e.g., Architect mode can't edit files)
• Truly model agnostic — Works with virtually any LLM provider, allowing cost optimization and model comparison
• Open source with funding — Apache 2.0 license means no vendor lock-in, while $5M funding ensures continued development
• MCP extensibility — Model Context Protocol integration allows connecting external tools and data sources
• Active community — Large Discord and Reddit communities provide rapid support and feedback

---

Cautions

• Stability concerns — Users report bugs appearing between releases as the team ships rapidly
• Token costs add up — BYOK model means users pay directly for API usage, which can be expensive with large contexts
• Cloud pricing complexity — $5/hour for cloud tasks can become costly for heavy team usage
• Fork origins — Some users prefer supporting the original Cline project
• Learning curve — Mode system and configuration options require time to master

---

Pricing & Licensing

Pricing as of archive time (May 2026); Roo Code Cloud has been shut down.

Licensing model: Open source (Apache 2.0) + SaaS cloud

Hidden costs: All LLM API costs are separate. Heavy usage with Claude or GPT-4 can easily exceed $100+/month in API fees.

---

Competitive Positioning

Direct Competitors

When to Choose Roo Code Over Alternatives

Roo Code is no longer a viable choice for new adoption — the extension is unmaintained and the repository is archived.

• Choose Cline when: You want Roo Code's official recommended migration path; Cline is the project Roo originally forked from
• Choose Kilo Code when: You want to keep Roo-style workflows; it forks Roo Code, reads existing .roomodes and .roo/rules/ config, and publishes a migration guide
• Choose Cursor when: You want a dedicated AI-native IDE
• Choose Tembo when: You need enterprise-scale agent orchestration
• Choose Roomote when: You want the same team's new Slack-based operational engineering agent rather than an IDE assistant

---

Ideal Customer Profile

Historical — Roo Code is no longer available for new adoption.

Best fit (at archive time):

• Individual developers wanting powerful AI assistance in VS Code
• Teams needing shared agent access via Slack/GitHub
• Cost-conscious users who want to choose their own LLM providers
• Developers who value open-source and extensibility

Poor fit:

• Enterprise teams requiring SOC 2 compliance (though Roo claims compliance)
• Users wanting simple plug-and-play without configuration
• Developers preferring AI-native IDEs over extensions

---

Viability Assessment

Roo Code is discontinued. The shutdown was announced on April 21, 2026, and the GitHub repository was archived after a final push on May 15, 2026, with about 24,200 stars and 3,300 forks at archive time. The team pivoted to Roomote, a Slack-based cloud agent priced at $899/month per parallel instance, arguing that cloud agents rather than IDE extensions are the future of AI-assisted development. Cline announced that Roo Code is "merging back to Cline," and Kilo Code published a Roo-to-Kilo migration guide the week the shutdown was announced.

---

Bottom Line

Roo Code is discontinued and not recommended for new adoption. The repository is archived, roocode.com redirects to roomote.dev, and no further development or support is coming.

Historically, Roo Code represented the evolution of open-source AI coding assistants from simple tools to full platforms; its mode system was a genuinely useful innovation for controlling agent behavior, and the Apache 2.0 license means the archived code remains forkable.

Recommended for: No one as a new adoption. Existing users should migrate — Roo Code's official recommendation is Cline , while Kilo Code offers a Roo fork that preserves .roomodes and .roo/rules/ configuration.

Not recommended for: Any new deployment; the extension is unmaintained and will not receive security or model updates.

Outlook: The product is dead, but its ideas persist — modes-style agent control lives on in Kilo Code, and its user base is folding back into Cline. The team's bet on cloud agents continues as Roomote, a separate Slack-based product rather than a successor to the extension.

---

Research by Ry Walker Research • methodology