The best alternatives to Kilo Code

Why look for a Kilo Code alternative

The praise that repeats is about governing spend rather than raw quality: the extension costs nothing, the source is in plain sight, and you supply the intelligence yourself, with your key, with a local model or through its gateway at provider rates. It lives in VS Code, in the JetBrains IDEs and on the command line, and agents with full tool access split a large task into subtasks on their own. The objections are about maturity and context. The JetBrains plugin runs several versions behind the VS Code one and started half a year later. Topping up credits carries a 5 % fee, so «no markup» only holds on the bring-your-own-key route. Since its 2025 launch it has carried the question of what it adds over the tools it came from. And it changed owner on 15 July 2026, which is too recent to know what it settles into.

What its own users repeat in the July 28, 2026 sweep:

• The JetBrains plugin runs several versions behind the VS Code extension and started half a year later (strong theme)
• Topping up credits carries a 5 % fee, so «no markup» only holds when you bring your own key (strong theme)
• Spend is not flat: it depends on the model you connect, and that demands a discipline a fixed fee never asks for (strong theme)
• The panel has no tabbed view for several tasks and the editor hands focus away when the agent creates a file (present theme)
• Since launch it has carried the doubt of what it adds over the tools it came from (present theme)
• Its site still says the licence is Apache-2.0 when the published package ships MIT, which is a slip on something that matters (present theme)

What the internet says about each alternative