Kilo Code
The open-source agentic engineering platform
5.0•46 reviews•6K followers
The open-source agentic engineering platform
5.0•46 reviews•6K followers
Build, ship, and iterate faster with the most popular open-source AI coding agent. 5M+ Kilo Coders. 10T+ tokens processed per month.
Follow us: kilo.ai/social
This is the 5th launch from Kilo Code. View more
Kilo Code for JetBrains
Launched this week
Kilo Code for JetBrains is a fully native, open-source coding agent for IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, PhpStorm, CLion, RubyMine — any JetBrains IDE. Designed for both local and remote dev, with parallel agents in isolated worktrees, GitHub PRs and diffs inline, and 500+ models.
Launch Team / Built With
Native Kotlin instead of reusing the VS Code build is a good call. Does each agent worktree make IntelliJ index all over again?
I mostly work solo so parallel agents sound like overkill at first glance until I remember how often I second-guess an approach halfway through. Being able to run two implementations at once and just pick the better one, without extra Git gymnastics is actually a solid use case even outside team settings.
Kilo Code
@yolanda_c_schneider yes, we will support for this too soon, it's already landed for VSCode and we will add it to JetBrains; By the way I'd recommend you to give the agent manager a shot, working on several things at the same time, all isolated is x2 x5 my productivity and it's more fun then just waiting for one agent to finish the job.
Kilo Code
more about the agent manager here btw: kilo.ai/features/agent-manager
I manage a small team split between PhpStorm and Rider and tool fragmentation has been a real headache. If this genuinely works the same way across both, that's not a nice-to-have for me, it's the actual reason I'd adopt it.
Kilo Code
We know the feeling. Teams can use @Kilo Code across @JetBrains IDEs, @VS Code, CLI, and cloud workflows, with centralized billing, usage analytics, model controls, role-based access, and enterprise identity features where required. The mission is to build an all-in-one, agentic AI platform that supports you wherever you are.
The isolated worktrees idea is clever for a reason people might overlook: it means I can let an agent experiment on a risky refactor while my main branch stays untouched. I've been burned before by agents making changes I couldn't cleanly roll back.
Kilo Code
@kimberly_west yes! and it makes you able to work on 5-6 tasks at the same time with a great UX without painful window switching.
The inline diff and PR review piece is what actually got my attention, not the AI part. I've reviewed plenty of PRs where the context-switching to GitHub's web UI broke my focus more than the review itself did.
Kilo Code
spot on! the inline diff is really helpful to get a local review as a sanity check before shipping to a public repo.
The worktrees setup is what sold me. I can run two agents on separate branches without stashing changes every five minutes. That used to eat half my afternoon during bigger refactors…
Kilo Code
thank you for your support! what should @Kilo Code launch next from your perspective? would love your input in this thread in /p/kilocode
CLion's plugin for agent has often left me unhappy because of how cumbersome it is to use the diff feature when you've already dug deep into C++ headers. But then, if the inline diff view in this case performs as well as it should, I'll happily leave that terminal window behind.