Kilo Code for VS Code - Parallel agents, diff reviewer, and multi-model comparisons

Kilo is becoming one of the few coding tools I actually keep coming back to.

@matheusgomes062 thank you! this just made my day 💛🖤

make sure to leave a review here: https://www.producthunt.com/products/kilocode/reviews/new

@matheusgomes062 thanks, that's great to hear! Also thank you for joining our webinar earlier today!

@matheusgomes062 Thank you! I agree - parallel tool calling makes the whole experience move much faster.

@matheusgomes062 that's great to hear, thanks for sharing!

oss ftw! make sure to star this repo

@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.

@jobrietbergen yes, and we're hanging out here, on Twitter/X and LinkedIn all day - ask us anything ✌️

@barnaby_lloyd it is only constrained by the hardware you’re running on.

@barnaby_lloyd It's constrained by machine resources

@barnaby_lloyd No limit, so it's a machine constraint if any!

ty! what's your favorite new feature in this release?

@th_calafatidis thank you, happy you like it!

@th_calafatidis Thanks a lot!

@boyuan_deng1 with the agent manager, each agent gets their own git worktree. That way they don’t conflict with one another. Then once they are done you can either open a PR directly from that worktree or have the agent merge it back into your local copy

@boyuan_deng1 There are two default subagents, general and explore. Explore tends to be utilized to find or answer a question about the codebase, and general can be used to make parallel edits but in a way that is directed by the parent agent to not cause conflicts (separate folders, modules, etc)

@boyuan_deng1 We use git worktrees to prevent conflict so that you can merge without issues!

Great questions! Fun fact: parallel agents was one of the bets in v7 that took the longest to get right.

Try it here:

vscode:extension/kilocode.kilo-code

Looking forward to your thoughts

@daniel_harris11 yes that’s the best part - each agent has their own context window. The parent agent passes only the context needed for the subagent to get its task done, and the subagent only passes the results back to the parent. All of the in between context doesn’t pollute one or the other

@daniel_harris11 Each subagent gets its own context, then provides a summarized report to the primary agent. You can view subagent sessions while they are running and the final report if you are interested.

@daniel_harris11 They each get their own when you're on separate worktrees (branching from the original agent), and can share when the work is merged back in :)

great question! also curious how many agents do you run in parallel?

@maltepruser lfg! what new feature are you most excited about?

@maltepruser thank you!

@maltepruser Thank you!

spot on! this team keeps shipping: @Kilo Code for @VS Code and @JetBrains, and more with @KiloClaw...

@erik_israni Kilo Speed!

@erik_israni Thank you! Glad you're enjoying it :)

Thank you, Josh!

@josh_slone1 thanks for joining us on the journey. What do you like most from the new version?

@josh_slone1 Thank you! Glad you're enjoying it.