Roo Code Is Dead. 3 Million Installs Disappear Overnight.

Roo Code announced it will archive its VS Code extension repo on May 15 and merge back into Cline, the project it originally forked from. CEO Matt Rubens said the team needs to "constantly destroy and recreate to keep up with what's newly possible." Translation: the extension model is dead to them, and they're betting everything on Roomote, their cloud agent product.

Three million installs. Gone. If you built workflows around Roo Code, you have three weeks to migrate.

This is the second major AI coding extension to exit the VS Code marketplace this year, and I think it tells a bigger story about where the market is heading. The IDE extension model has a fundamental problem: you're competing on a surface area that the IDE vendor controls. VS Code can change APIs, Copilot gets preferential integration, and you're always one update away from breakage. Roo looked at that landscape and decided the cloud agent model, where you own the full stack from inference to execution, was more defensible.

Cline confirmed they're absorbing the merge, so Roo users have a direct migration path. But I'd use this as a moment to evaluate your whole tooling setup. The JetBrains AI Pulse survey of 10K+ developers shows the market is consolidating fast: GitHub Copilot at 29% (but stalling), ChatGPT at 28%, Claude Code at 18% (6x growth from ~3% in mid-2025, 91% CSAT, 54 NPS). Google's Antigravity hit 6% in just two months from launch. The smaller players are getting squeezed.

The meta-pattern here: tools built as wrappers around someone else's infrastructure are fragile. Roo was a wrapper around VS Code's extension API calling third-party LLMs. When both layers shift underneath you, there's nothing stable to stand on. If you're building on AI coding tools, build on the ones that own their stack. Or better yet, build workflows that aren't locked to any single tool. The ctx project that lets you start work in Claude Code and continue in Codex exists for exactly this reason.