Kilo Code for JetBrains

Finally, Kilo for Jetbrains 🎉

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.

This looks like a solid step for Ai-assisted coding, How does kilo code handle large and more complex codebase?

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?

Inline GitHub PR review sounds small until you've spent an hour tab-switching between your editor and browser just to leave a comment. If this actually keeps me in Rider while reviewing, that alone is worth trying.

@Kilo Code is so back on @Product Hunt.Four months ago, the team launched a new @VS Code extension. #1 Product of the Month, the community loved it.Today, we’re shipping a native plugin for @JetBrains. Rebuilt from the ground up in Kotlin with Swift UI, designed for both local and remote dev, the plugin brings first-class AI coding assistance to IntelliJ IDEA, WebStorm, PyCharm, and other JetBrains IDEs: parallel agents, GitHub PRs and diffs inline, 500+ models...View source code on GitHub: github.com/kilo-org/kilocodeLooking forward to seeing what you're building with @Kilo Code.