
Kilo Code
The open-source agentic engineering platform
5.0•46 reviews•5.8K followers
The open-source agentic engineering platform
5.0•46 reviews•5.8K followers

Kilo Code for JetBrains





5.8K followers
5.8K followers





Launched on May 5th, 2026
Launched on January 27th, 2026
Launched on September 28th, 2025
Launched on March 27th, 2025
BuildShip
This is excellent! Been waiting for something like this for a long time!
Kilo Code
amazing! looking forward to seeing what you're building with @Kilo Code. make sure to add your review here: producthunt.com/products/kilocode/reviews
fn7 Helix
Native Kotlin instead of reusing the VS Code build is a good call. Does each agent worktree make IntelliJ index all over again?
UTCP
Congrats on the launch @fmerian, looks very cool!
Kilo Code
@aliraza36580 thank you for your support, Ali. absolute fan of your work at @UTCP. oss ftw!
What has surprised you most about how developers are using the paltform?
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.
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.