I wrote about Roo Code’s extension shutdown a few weeks back, treating it as a serious but potentially recoverable setback. It wasn’t recoverable. As of this month’s tracking, the actual GitHub repository is archived — not just the published extension pulled from the marketplace, but the source itself frozen, no further commits possible through the normal flow.

The full timeline, now that it’s actually complete: the VS Code extension itself stopped working on May 15, 2026 — the date I covered originally. The repository stayed technically alive for a while after that, in the state a lot of abandoned-but-not-quite-dead projects sit in: no extension you could install, but a codebase still there, still forkable, with at least the theoretical possibility of a community fork picking it up. That possibility is now closed. Archiving a repository is GitHub’s explicit “this project is done” signal — read-only, no new issues, no new pull requests through the normal path.

Why this matters beyond just one tool disappearing: I’ve recommended alternatives to Roo Code more than once on this site, and every one of those recommendations was written against a tool that, at the time, still technically existed even if its extension was down. That’s no longer true, and it’s worth being direct about what actually changes for anyone who was still holding out hope: there’s no scenario left where Roo Code itself comes back. The two paths for anyone in that position are the same two I named in the alternatives post — ZooCode, the direct community fork that picked up where the original left off, or moving to an actively maintained tool like Cline or OpenCode entirely.

The broader pattern worth naming: this is the second major tool this month I’ve had to walk back or close out after initially covering it as active — I did the same with Aider’s maintenance status a few days ago. Neither closure happened suddenly; both showed the warning signs first — a shutdown before an archive, a stalled release cadence before a full stop. If you’re relying on any tool in this space, the actual health signal worth watching isn’t whether it currently works, it’s whether commits and releases are still landing on anything like a normal cadence. Roo Code gave months of warning between “extension down” and “repository archived.” The warning was just easy to miss if you weren’t specifically watching for it.