Kilo is easier to recommend honestly when we start from the official product pages checked on April 16, 2026 instead of repeating older directory text. The official homepage now calls it the open-source AI coding agent for VS Code, JetBrains, and your CLI. That matters because it immediately corrects the older English page, which felt too generic and too narrow. Kilo is no longer best described as a small local-first helper. The official product story is much broader than that.
The homepage also makes Kilo’s surface area much clearer than the current English page does. In the Use Kilo Everywhere section, the official site lists VS Code, JetBrains, CLI, Cloud Agents, App Builder, Slack, Code Reviewer, Gateway, and Gastown. That means Kilo should be judged as an engineering workflow platform rather than only as one IDE extension. For readers deciding whether to install it, this is an important correction because it explains why Kilo may feel more ambitious than simpler coding assistants.
The sync story goes even further. The same homepage says users can start a task on a mobile device and finish it in VS Code, JetBrains, or the CLI without missing a beat, and it says session history, active agents, and variables follow automatically across devices and environments. This is one of the strongest reasons the current English page needs rewriting. If the official product promises cross-device continuity and persistent context, then calling Kilo merely local-first undersells the current product shape. Our grounded judgment is that Kilo now leans toward continuity across interfaces, not minimalism inside one editor.
Provider choice is another area where the official docs are far more concrete than the current page. The Setup & Authentication docs say Kilo Code supports over 30 providers and give examples such as ChatGPT Plus or Pro with no API key, OpenRouter, Anthropic, and OpenAI. The same page also points to broader options including Google Gemini, DeepSeek, Mistral, Ollama, AWS Bedrock, and Google Vertex. That matters because Kilo is not only selling a single model relationship. It is selling a workflow that can sit on top of several billing and infrastructure choices.
Kilo’s openness story is also worth describing more carefully than the old page did. The official Open Source Commitment page says Kilo Code is open and highlights Apache-2.0 licensing, while linking the VS Code extension, JetBrains extension, and CLI repositories. It also says features that are open source today stay open source tomorrow, promises continued BYOK support, and says gateway and cloud backend source is available, with abuse-protection systems excluded for security reasons. This is a more nuanced and more trustworthy story than simply calling the whole product open source with no detail.
The installation docs are equally important for a practical recommendation. On the official install page, Kilo says the current VS Code extension is built on the Kilo CLI and distributed as the pre-release version on the VS Code Marketplace. The same docs are careful to say that the pre-release label is only the Marketplace distribution channel and that the extension is stable and recommended for all users. They also document Open VSX and direct VSIX installs for compatible editors. That is a strong reason to replace the thin old download guidance with something current and specific.
The CLI docs are even more straightforward. They recommend installing the CLI with npm install -g @kilocode/cli, warn that older CPUs without AVX support may need a baseline build from GitHub releases, and tell users to run kilo and use /connect for first-time provider setup. This is practical advice that directly reduces setup friction. It also shows that Kilo’s CLI is a real first-class surface, not only a technical side note behind the IDE experience.
JetBrains users also need a clearer summary than the current page provides. The official JetBrains docs say Kilo Code supports IntelliJ IDEA, WebStorm, PyCharm, and more, but they also list two setup prerequisites that should not be hidden: JetBrains Toolbox is recommended because authentication callbacks work properly with it, and Node.js LTS is required for the extension’s backend services. That does not make JetBrains support weak, but it does mean the page should be honest that the JetBrains path is a little heavier than a casual one-click install.
The official free-usage docs add one more important correction. Kilo says it can be used completely free of charge, but the docs are explicit that model inference appears in three places: agentic interactions, autocomplete, and background tasks. They recommend Auto Model Free for agentic use, explain that free autocomplete can be set up with a Mistral Codestral key through BYOK, and say background tasks need the small model switched to a free model if users want zero credit usage there too. This is much more helpful than vague marketing because it tells readers where the real setup work is.
The release feed gives the final grounding point. On April 16, 2026, the latest official GitHub release endpoint for Kilo-Org/kilocode returned v7.2.10, published on April 15, 2026. The release assets included CLI archives such as kilo-windows-x64.zip and kilo-windows-x64-baseline.zip, plus VSIX packages such as kilo-vscode-win32-x64.vsix. That fits the official product story well: Kilo is maintaining both terminal and editor distribution paths at the same time.
Our grounded judgment is that Kilo is most worth trying for developers or teams who want one AI coding layer across VS Code, JetBrains, and the CLI, and who care about provider choice, BYOK flexibility, and a broader workflow surface that can extend into cloud agents and review flows. It is less suitable for people who only want a tiny zero-setup autocomplete helper or who specifically want a purely offline and purely local coding assistant with minimal platform behavior. Kilo now has enough surface area that setup choices, provider choices, and interface choices should be treated as part of the product, not as side details.
