Roo Code went dark on May 15, 2026. The VS Code extension that developers used to automate refactors, scaffold projects, and argue with AI about whether their code was actually correct — discontinued without warning. The maintainer walked away. The community scrambled.

But in April, before Roo Code even showed signs of dying, a team had already forked it and started rebuilding. They called it Kilo Code. By the time the original was officially discontinued, Kilo had a portable open-source core, an MIT-licensed CLI, and a roadmap that looked nothing like a fork. It looked like a platform.

Not Just a Fork Anymore

Kilo Code started as a fork of Cline — the open-source coding agent that became a de facto standard for developers who didn't want to pay Cursor's subscription or commit to GitHub Copilot's ecosystem. When Roo Code emerged from Cline's lineage and then died, Kilo absorbed the best ideas from both and went further.

The architecture now supports 500+ AI models from 60+ providers. That's not a selling point you'll see in Copilot's marketing. GitHub's copilot is a single model family. Anthropic's Claude Code is Anthropic-only. Kilo is model-agnostic by design — you pick the model, you pick the provider, and the agent runs the same way regardless.

That matters for teams. A enterprise running a fine-tuned code model on their own infrastructure doesn't want to switch IDEs to use it. Kilo runs in VS Code, JetBrains IDEs, the CLI, and — this is the part that gets less attention — on mobile and in Slack. It's the first serious attempt at a cross-surface coding agent that treats the IDE as one surface among several, not the entire experience.

What Open-Source Actually Gets You

The proprietary coding agents have UX. Kilo has auditability. Apache 2.0 licensed means any team can inspect the prompts, the context assembly logic, the tool definitions, and the orchestration layer. You can fork it. You can modify it. You can run it without an internet connection and without sending your codebase to a third-party API.

For regulated industries, that's not a nice-to-have. A financial services firm that wants to deploy an AI coding agent against their trading infrastructure can't do it with a hosted model they don't control. Kilo lets them own the stack.

It's also the reason Kilo's agent supervisor infrastructure — subagents, the Agent Manager, the orchestration layer — gets less coverage than it deserves. The community is building the harness engineering layer that the proprietary tools lock away. When something breaks or behaves unexpectedly, you can trace it. That's different from filing a support ticket and waiting.

The Competitive Math

Cursor's valuation is real. The funding rounds are real. The teams using it daily are real. But Kilo's growth is also real — and it's driven by a developer base that is deeply uncomfortable with the proprietary SaaS trajectory of the major coding agents.

Every time Cursor raises prices, every time Copilot changes its training data policy, every time a proprietary agent maker decides to pivot their business model, there's an exodus. Kilo is the landing spot. Not because it's better in every dimension — the UX on Cursor is genuinely better in many ways — but because it solves a different problem. It's not trying to be the best AI coding tool. It's trying to be the most open one.

The comparison pages on kilo.ai make this explicit: Kilo vs. Cline, Kilo vs. Roo Code, Kilo vs. Claude Code. They're not shying away from the comparison shopping. They want you to look at the feature matrix and decide for yourself.

What's Next

GitHub's awesome-harness-engineering list — a community-curated collection of tools, patterns, evals, memory systems, MCP integrations, permissions frameworks, and orchestration approaches — crossed 2,000 stars in June. The infrastructure layer for AI agent engineering is maturing fast, and Kilo is one of the few projects actively absorbing that maturation into a coherent product.

The real test comes in the next six months. As Kilo grows its team user base — where one license covers an entire dev team working in shared environments — the gaps in orchestration, access control, and audit logging will become more apparent. The open-source model is an advantage until it isn't. The projects that close those gaps fastest will own the enterprise tier.

Roo Code died because it couldn't sustain the maintenance burden with a small team and no business model. Kilo inherited that problem and added more surface area to cover. Whether the community can sustain it — or whether a company wraps around it — is the next chapter.

For now, if you're a developer who wants to own your AI coding stack, Kilo is the most serious option that's ever existed in this space. That wasn't true six months ago.