Kilo Code v7 for VS Code - Parallel agents, diff reviewer, and multi-model comparisons
by•
We've completely rebuilt Kilo Code for VS Code, built on OpenCode server. New portable core, parallel tool calls, subagent delegation, inline code review, multi-model comparisons. Get started: kilo.ai/install
Replies
Looking forward to seeing what you're building with @Kilo Code!
Kilo Code
@fmerian thank you, what's your favorite new feature in this release?
@jobrietbergen multi-modal comparisons are so helpful. there's an always-on debate on what the best AI models for coding are. [1] now we know.
[1]: What's the best AI model for coding?
Kilo Code
@fmerian yeah that's very helpful to benchmark performance across different tasks
KiloClaw
Hey Product Hunt 👋 Brian from Kilo Code here.
We just shipped the biggest update to our VS Code extension since launch. The entire thing has been rebuilt on OpenCode server, which is the same open-source core that powers our CLI and Cloud Agents. One engine across every surface, so when we improve something, it gets better everywhere.
The headline feature is real parallelism. Kilo can now run multiple tool calls at the same time (file reads, searches, terminal commands all firing concurrently), and it can spin up parallel subagents that each handle a piece of a larger task simultaneously. You actually feel the speed difference.
A few other things shipping in this release:
Agent Manager — run multiple independent agents in separate tabs, give each one a role, and use git worktrees so they never step on each other's code
Inline code review — leave line-level comments directly on agent diffs, just like a PR review, and send them back as structured context
Multi-model comparisons — run the same prompt through different models side by side and pick the best result
Cross-platform sessions — start in the CLI, pick up in VS Code, share with a teammate
Kilo is open source, runs 500+ models at provider cost (zero markup), and has over a million developers using it. We'd love for you to try it out and tell us what you think!
Kilo Code
@brian_turcotte agent manager is such a great addition, and overall it works so much faster! Great to be working together on this one!
@brian_turcotte @jobrietbergen great product. great team. period.
Kilo Code
@brian_turcotte @fmerian 🫶
@brian_turcotte curious what's your @VS Code look like? any extensions you'd recommend in addition to @Kilo Code?
KiloClaw
@fmerian I added a front-end specialist skill from skills.mp, but other than that - the vanilla extension is all I need for my work!
ClawSecure
@brian_turcotte One engine across CLI, VS Code, and Cloud Agents is the right architecture. We run agent workflows across multiple surfaces internally and the biggest friction is always inconsistency between environments. Something works in the terminal, behaves differently in the editor, breaks entirely in cloud. A unified core that improves everywhere simultaneously solves that at the infrastructure level.
Real parallelism is the feature that matters most here. Sequential tool calls are the hidden bottleneck in most agentic coding workflows. When a complex task requires reading 10 files, searching a codebase, and running terminal commands, doing that one at a time turns a 30-second task into a 5-minute wait. Parallel subagents handling pieces of a larger task simultaneously is where the speed compounds even further, especially on architectural work that naturally decomposes into independent subtasks.
The Agent Manager with git worktrees is a smart detail. We've run into the exact problem of multiple agents stepping on each other's code. Isolating each agent in its own worktree so they can operate independently without merge conflicts is the kind of practical engineering decision that shows you've actually dealt with multi-agent workflows in production, not just theorized about them.
Inline code review on agent diffs is great too. The gap between "agent generates code" and "human approves code" is usually copy-paste into a PR tool. Doing it directly in the editor with structured context going back to the agent tightens that feedback loop significantly.
Open source at provider cost with zero markup across 500+ models. Hard to argue with that. Congrats on the release.
KiloClaw
@jdsalbego Thank you very much for the thoughtful comment!
ClawSecure
@brian_turcotte Of course! Been following your products' development since you guys started. Big fan.
@brian_turcotte Hey Brian, what stops two subagents from making contradictory edits to the same file when they're working on related parts of a task? You mentioned git worktrees for the Agent Manager; is the same isolation used for subagents, or is there a different mechanism?
@brian_turcotte congratulations on the release! I am new to Kilo Code but am looking forward to trying it out. I commented under@kzhao post because I am also curious about this, and would you still "recommend" agents work on separate tasks or even separate files when possible to avoid conflicts or is the Agent Manager able to handle?
KiloClaw
@kzhao Exactly - it's git worktrees for Agent Manager, and with subagents it depends - if the tool calls won't conflict or aren't actually writing code (such as read or plan agents), worktrees aren't required.
Kilo Code
@kzhao @brian_turcotte @blaize_olle I'd just add that subagents are delegated by a parent agent mainly to keep its context focused - they go do the work, and return a summary to the parent rather than the full tool-call history. They share the parent's workspace rather than getting their own worktree, so the safeguard against contradictory edits there is the parent orchestrating: subagents are best used for scoped exploration and well-bounded changes, while the parent integrates.
Where Agent Manager really shines is when the tasks are already structurally independent (e.g., different features, different files, or "throw the same prompt at three models and pick the best result") - it gives you one surface to track all of them, see PR/review status, and prune what you don't want.
More on that in our livestream that aired earlier today and is now available on demand. Marius, the engineer behind Agent Manager, breaks it down here (jump to 18:00) https://app.livestorm.co/kilocode/kilo-show-for-coders
Chengyu Wordle
Been using v7 for a while, and even the versions before this. Took a while to get used to, but generally excited to see it being built on OpenCode. Can't wait for more features especially /remote 🤞🙏
@cheeaun love to read this, Lim! make sure to leave a review here and help us spread the word on X 💛🖤
Kilo Code
@cheeaun thank you for using Kilo!
KiloClaw
@cheeaun Thank you! Glad you're vibing with it ;)
Came from Roo Code a few months ago and honestly haven't looked back. The migration was smoother than expected. Good luck for today!
Kilo Code
@olivia_bennett7 happy to hear you like it. Have you tried agent manager already to put multiple agents to work?
Your words just made our day, Olivia!
For anyone else reading this and coming over from Roo Code, the team wanted to make this as easy as possible. They crafted a migration guide that walks through bringing settings, modes, and workflows into Kilo here: kilo.ai/roo-migration
Enjoy! and make sure to leave a review here: producthunt.com/products/kilocode/reviews/new
KiloClaw
@olivia_bennett7 Love to hear that! Thank you!
If one agent is refactoring an API and another agent is consuming that API, how do they handle the dependancy? Do they share context live or waiting for human reviews?
Kilo Code
@michael_vavilov you can use agent manager to let agents run on separate git worktrees so they don't interfere with each other. You can then review locally and in the cloud with Kilo, and resolve any merge conflicts.
KiloClaw
@michael_vavilov They use git worktrees to avoid conflict and share context upon merge!
Kilo Code
@anusuya_bhuyan they run simultaneously!
framing this!
Kilo Code
@anusuya_bhuyan it runs them simultaneously on separate worktrees
KiloClaw
@anusuya_bhuyan Either!
You can run them in parallel inside the Agent Manager or just start a new branch and run them sequentially.
apideck
Using Kilo for Resume Matcher. Works really well, however, ƒor this launch. I'd suggest some features that Kilo should add. The first one is Skills, just like Claude-Code. A .kiloignore, and custom routines to be fired up to check for dependencies, security risks, and other supply chain attacks that may be in transitive dependencies. Because the more we vibe-code, the better the security should be, and the more exhaustive the reviews should be.
@srbhr big fan of your work, Saurabh! what do you enjoy the most with @Kilo Code?
appreciate the feedback 💛🖤 cc @brian_turcotte
apideck
@brian_turcotte @fmerian thanks.
Kilo is customizable, both on coding and PR reviews. I'm using it mainly for PR reviews, right now.
Kilo Code
@srbhr thanks for using Kilo and your feedback. We do support skills, and we also have our marketplace! https://kilo.ai/docs/customize/skills#finding-skills. We agree security matters! We have been working on a few features in that space: https://kilo.ai/features/security-agent, If you have further feedback please let us know on our GitHub repo!
direct link to the gh repo icymi: https://github.com/kilo-org/kilocode
apideck
@jobrietbergen Awesome, I'll test the Security part really soon.
@jobrietbergen @srbhr keep us posted! and make sure to leave a review here: https://www.producthunt.com/products/kilocode/reviews/new
KiloClaw
@srbhr Thanks for the feedback! Both Skills and .kiloignore are currently supported in v7 - nice callout!
Triforce Todos
@abod_rehman thank you, great to hear you like the inline diff reviewer. I use the code reviewer in VS Code before creating a PR, and let the code reviewer in the cloud check everything again. For small changes (and screens, since I do a lot of that on mobile) I usually kick if off from Slack or cloud agents, and then have the code reviewer in the cloud do the check.
love it! give it a spin at kilo.ai/install and let us know how it goes with a review here: https://www.producthunt.com/products/kilocode/reviews/new
looking forward to it!
KiloClaw
@abod_rehman Thank you!
Yes it does still support split views - even with multiple agents running!
oss ftw! make sure to star this repo
Kilo Code
@hamza_afzal_butt thank you!
Unlike Copilot and Cursor we don't limit you on models to use. You can start by using plan mode inside Kilo, to iterate on a plan together with the agent. When you're ready to implement it, switch to code mode. Then the agent implements your plan, and asks you questions if needed. When the agent is ready you can let a local code reviewer check the changes. We also just released semantic indexing so your agent has better context.
fwiw below are full breakdowns:
vs Cursor
vs GitHub Copilot
hope it helps!
Kilo Code
Hey Product Hunt 👋 - Job from the Kilo team.
Very excited for this launch. The new Kilo for VS Code is my daily driver, and this rebuilt version with agent manager is in my opinion the next step in agentic coding. I now let multiple agents run at the same time using agent manager, and it speeds up my workflow a lot. Super curious to hear what you think of it!
🚨 We're also hosting 2 live sessions TODAY:
•
10am EST | The Kilo Show for Non-Coders
We'll talk marketing automation, SEO, competitive analysis, and design
Register →
•
11am EST | The Kilo Show for Coders
We'll talk agent orchestration, codebase indexing, and IDE workflows
Register →
@jobrietbergen yes, and we're hanging out here, on Twitter/X and LinkedIn all day - ask us anything ✌️