Kilo Code

Kilo Code is the clearest winner to come out of the open-source coding-agent reshuffle of 2026. When Roo Code was archived on May 15, the community did not scatter — it consolidated. Kilo Code was built by forking both Cline (the most-installed open-source VS Code coding extension, north of five million installs) and Roo Code, then merging their best features under one actively maintained project. The unusual part: the official Roo Code team publicly points users to Kilo as the place to go. That kind of endorsement from the project you forked is rare, and it tells you the handoff was cooperative rather than hostile.

The core proposition is freedom with no markup. The plugin itself is permanently free and open source. In bring-your-own-key (BYOK) mode you pay only the AI provider’s API fees — Anthropic, OpenAI, Google, OpenRouter, local models, whatever you like — with zero markup added by Kilo. Over 500 models are supported across VS Code, JetBrains IDEs, and a standalone CLI, which means Kilo covers essentially every mainstream development environment from a single configuration. For developers who resent being locked into one vendor’s model and one vendor’s pricing, this is the antidote.

The feature that lifts Kilo above a generic Cline reskin is Orchestrator mode. Instead of throwing one model at a sprawling task, Orchestrator decomposes the work into subtasks and routes each to a specialist mode: Architect for planning, Coder for implementation, Debug for testing and fixes. You can watch it plan, build, then verify, with the right “persona” handling each phase. This is the same multi-agent decomposition that Google is selling inside Antigravity and that Claude Code approximates with subagents, except here it is open source and model-agnostic. You can run the planning step on an expensive frontier model and the mechanical edits on something cheap, which is exactly the cost-control lever BYOK is supposed to give you.

Pricing deserves a clear-eyed look because “free” has an asterisk. The plugin costs nothing and Kilo seeds new users with $20 in free credits. But in BYOK mode your real bill is whatever your provider charges, and you own the rate limits and the monthly statement. If you would rather not manage keys, Kilo sells optional cloud services: KiloClaw at $9/month (with a one-week trial), a Teams plan at $15/month, and Kilo Pass inference-credit packs starting at $19. Those are genuinely cheap relative to a Cursor or Copilot subscription, but they are add-ons, not the headline product. The headline product is the free, open agent you point at your own keys.

How does it compare to the tools PixlRun already covers? Against Cursor, Kilo trades a polished proprietary UI and tightly-tuned default model for total transparency and zero lock-in — Cursor is smoother out of the box, Kilo is cheaper and more flexible once you have your keys sorted. Against Cline and the now-archived Roo Code, Kilo is simply the merged superset that is still being maintained, which makes the choice between those three easy. Against Claude Code, the comparison is philosophical: Claude Code is a single, exceptionally strong harness wedded to Anthropic’s models; Kilo is a harness that will run any model you give it, including Anthropic’s. If you want one outstanding default, Claude Code; if you want a Swiss-army agent you control end to end, Kilo.

The trade-offs are real and worth stating plainly. BYOK is freedom and homework at the same time: you configure providers, you watch the spend, you eat the rate limits when a provider throttles you. Because Kilo ships no first-party model, the quality you get is entirely the quality of the model you wire in — a weak provider makes Kilo look weak, and that is on you, not the tool. And the genuinely hands-off cloud experience is the paid KiloClaw tier, not the free plugin.

For developers who are comfortable holding their own API keys, Kilo Code is close to a no-brainer in 2026: it is free, it is open, it runs everywhere, it supports more models than anything else, and its Orchestrator mode brings real multi-agent structure without a subscription. It is the tool we would hand to a cost-conscious engineer who wants frontier-model power without frontier-model lock-in.

How we would use it. Kilo Code is the agent we would hand a cost-conscious engineer who already holds API keys and resents lock-in. Point Orchestrator’s planning step at a frontier model, route the mechanical edits to something cheap, and you get multi-agent structure at provider cost with zero markup — the same decomposition Antigravity sells, but open and portable across VS Code, JetBrains, and the CLI. The homework is real: you own the keys, the spend, and the rate limits, and a weak provider makes Kilo look weak. But for teams that want to standardise on one open harness and swap models freely as the frontier moves, Kilo is the safest long-term bet in the open-source tier right now — actively maintained, endorsed by the project it forked, and free where it counts.