Cline vs Roo Code vs Kilo Code
Roo Code is discontinued — the repository is archived and there are no more fixes. The real question is which of the two live projects you migrate to.
Updated August 28, 2026 · Independent comparison — Cline, Roo Code, Kilo Code are separate products.
Cline
Apache-2.0 agent for VS Code and JetBrains
Cline is Apache-2.0 licensed and runs in VS Code, JetBrains, a CLI and an SDK. It is built around bring-your-own-key for any provider, with two first-party options layered on: Cline's own usage billing, and ClinePass at $9.99/month for thirteen open-weight models. Its harness features — Plan and Act modes, MCP support, checkpoints and browser checks — are the reason people pick it over a thinner CLI.
Roo Code
Discontinued May 2026 — repository archived
Roo Code was an Apache-2.0 fork of Cline that ran in VS Code, and it is no longer a live product: it shut down in May 2026 and its repository is archived, with the team moving to Roomote, a Slack-based product. If you are running it today it still works, but it is unmaintained and receives no fixes. The two supported migration paths are Cline, the project it originally forked from, and Kilo Code, which reads Roo's .roomodes configuration.
Kilo Code
Open-source agent, Roo Code's successor
Kilo Code is the designated successor to Roo Code and reads .roomodes files directly, which makes migration close to mechanical. It is open source, was acquired by Anaconda around July 2026 and remains so, and runs in VS Code, JetBrains, a CLI, Slack and cloud agents. Its gateway reaches 500+ models at pass-through rates with no markup, alongside conventional bring-your-own-key and local Ollama or LM Studio backends.
Bottom line
Roo Code is no longer a live product: it shut down in May 2026, its repository is archived, and the team moved to Roomote, a Slack-based product. If you are still running it, it works but is unmaintained. There are two supported destinations. Cline is the Apache-2.0 project Roo originally forked from, runs in VS Code, JetBrains, a CLI and an SDK, and adds first-party billing options including ClinePass at $9.99/month for thirteen open-weight models. Kilo Code is the designated successor: it is open source, was acquired by Anaconda around July 2026, reads Roo's .roomodes configuration directly — which makes migration close to mechanical — and its gateway reaches 500+ models at pass-through rates with no markup.
Status & licence
| Feature | Cline | Roo Code | Kilo Code |
|---|---|---|---|
| Status | Active | Discontinued May 2026 — repository archived | Active — acquired by Anaconda around July 2026 |
| Licence | Apache-2.0 | Was Apache-2.0, a fork of Cline | Open source (MIT per the project; confirm against the repository) |
| Price | Free; ClinePass $9.99/month is optional | Free, but unmaintained | Free; gateway usage at pass-through rates |
Where and how it runs
| Feature | Cline | Roo Code | Kilo Code |
|---|---|---|---|
| Where it runs | VS Code, JetBrains, CLI, SDK | No longer maintained | VS Code, JetBrains, CLI, Slack, cloud agents |
| Model support | Any provider via BYOK, plus ClinePass | Whatever you had configured; no new provider support | 500+ via the Kilo Gateway at pass-through rates; BYOK; Ollama and LM Studio |
| BYOK | ✓ | Historically yes | ✓ |
| Subscription support | Optional — ClinePass at $9.99/month | None | Optional gateway credits |
Capabilities
| Feature | Cline | Roo Code | Kilo Code |
|---|---|---|---|
| Parallel sessions | Not published | Not applicable | Not published |
| MCP support | ✓ | Historically yes | ✓ |
Verdict at a glance
| Feature | Cline | Roo Code | Kilo Code |
|---|---|---|---|
| Standout feature | Plan and Act modes, checkpoints and browser checks | Nothing current — migrate to Cline or Kilo Code | Reads Roo Code's .roomodes, so migration is near-mechanical |
The Verdict
Choose Cline if...
- ✓You want the upstream project Roo was forked from, with the longest track record
- ✓You want Plan and Act modes, checkpoints and browser checks
- ✓ClinePass at $9.99 for thirteen open-weight models is attractive
- ✓You need a JetBrains plugin as well as VS Code
Choose Roo Code if...
- ✓Nothing — it is discontinued and archived
- ✓If you are still running it, it works but receives no fixes or new provider support
- ✓Migrate to Cline for the upstream lineage, or Kilo Code for configuration compatibility
Choose Kilo Code if...
- ✓You want the least disruptive migration — Kilo reads .roomodes directly
- ✓You want a zero-markup gateway across 500+ models
- ✓You want local models via Ollama or LM Studio alongside hosted ones
- ✓You want Slack and cloud agents as well as VS Code and JetBrains
- ✓Anaconda's backing since July 2026 reassures you about maintenance
Frequently Asked Questions
What is the difference between Cline, Roo Code and Kilo Code?
Cline is Apache-2.0 licensed and runs in VS Code, JetBrains, a CLI and an SDK. Roo Code was an Apache-2.0 fork of Cline that ran in VS Code, and it is no longer a live product: it shut down in May 2026 and its repository is archived, with the team moving to Roomote, a Slack-based product. Kilo Code is the designated successor to Roo Code and reads .roomodes files directly, which makes migration close to mechanical.
Which of Cline, Roo Code and Kilo Code should I pick?
Choose Cline if you want the upstream project Roo was forked from, with the longest track record. Choose Roo Code if nothing — it is discontinued and archived. Choose Kilo Code if you want the least disruptive migration — Kilo reads .roomodes directly.
1DevToolRun them side by side instead of choosing
These agents are not mutually exclusive — they are processes, and most developers end up wanting two or three for different jobs. 1DevTool runs Claude Code, Codex CLI, Cline, OpenCode and Gemini CLI in persistent terminals in one window, each on its own subscription or key, plus an HTTP client, a 13-engine database client and an embedded browser. One-time $29, no subscription.