Kilo Code for JetBrains

Fully native, open-source coding agent built for JetBrains

Open Source

Software Engineering

Developer Tools

GitHub

Visit WebsiteSee on Product HuntGithub ⧉

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.

Congratulations on the release! Inline GitHub pull request diffs in PyCharm is something that I have been looking for in my review process.

I have been waiting for a JetBrains plugin that is not just a port of VS Code to JetBrains. Having a native Kotlin build makes all the difference to me now.

The truth is that it being entirely native and not another Electron-based extension makes a difference far more than people think it does. The JetBrains IDEs themselves are quite heavy to begin with.

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…

I switched from VS Code extensions mainly because I’m in PyCharm all day. Having a native agent instead of a webview bolted on finally feels right.

Congrats on the launch @fmerian, looks very cool!

Really happy to ship Kilo for JetBrains today. JetBrains built the best IDEs in the world (I was part of the original IntelliJ IDEA team back in the day 🤓), and with @Kilo Code we're making them agentic powerhouses.

We move at Kilo speed and dogfood hard — we build the plugin with the plugin — so please try it and tell us what's broken or missing. Feedback goes straight into the next release.

Love that this is a fully native Kotlin rebuild rather than a webview wrapper, and running parallel agents in isolated worktrees is a genuinely smart touch for keeping real projects clean.

Native is the key word here. I've tried extensions that just wrap a web view inside JetBrains and they always feel bolted on.

I've bounced between three JetBrains IDEs this year and always missed proper AI tooling on Rider. Genuinely excited this exists now.

I'm cautiously optimistic here. Local and remote dev support sounds great on paper but I've had "remote-ready" tools that fell apart the moment latency got involved especially with larger codebases.

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.

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.

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.

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.

My honest question: how well does this handle CMake-heavy projects with custom toolchains, not just simple scripts?