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
ZapDigits
WooW this feels really fast.
@malithmcrdev this is kilo speed ™️
Kilo Code
@malithmcrdev happy you like it, speed is a major differentiator of this release yea!
KiloClaw
@malithmcrdev Thank you!
Does the agent manager have any limits on how many parallel agents you can run at once, or is it just constrained by your machine's resources?
Kilo Code
@barnaby_lloyd it is only constrained by the hardware you’re running on.
@realolearycrew for example, what's your setup and how many agents do you run in parallel?
Kilo Code
@barnaby_lloyd It's constrained by machine resources
KiloClaw
@barnaby_lloyd No limit, so it's a machine constraint if any!
The parallel subagents with git worktree isolation is the part that actually makes sense to me. Every other tool just runs agents on the same files and hopes for the best. Congrats on shipping this!
Kilo Code
@asher_luca thank your for being a user!
spot on! help us spread the word on LinkedIn, repost this
KiloClaw
@asher_luca Thank you!
Just curious, when multiple subagents are running in parallel, how does the merge back to the parent agent work? Does it ever create conflicts when two agents touch overlapping parts of the codebase?
Kilo Code
@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
Kilo Code
@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)
KiloClaw
@boyuan_deng1 We use git worktrees to prevent conflict so that you can merge without issues!
How does Kilo handle context limits when you've got multiple subagents running on a large codebase? Does each subagent get its own context window or do they share?
Kilo Code
@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
Kilo Code
@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.
KiloClaw
@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 :)
Krater.ai
Niiiice! Looks amazing and clean
@maltepruser lfg! what new feature are you most excited about?
Kilo Code
@maltepruser thank you!
KiloClaw
@maltepruser Thank you!
definitely! read this full breakdown: kilo.ai/kilo-code/vs/claude-code
TL,DR: @Kilo Code is open-source, offers multi-model CLI + IDE agent with inline autocomplete vs Anthropic's Claude-only terminal-first coding agent.
eager to have your feedback!
Kilo Code
@lakshminath_dondeti i might be biased, but you definitely should ;) - you can also use your codex subscription inside of Kilo, or use any of the free/frontier models
@jobrietbergen oss ftw!
KiloClaw
@lakshminath_dondeti I certainly think so!
In addition to freely switching models, we're also completely open-source and focused on frictionless agentic orchestration. The openness combined with parallel execution makes it a different experience than other tools, in my humble opinion!
Been on Cursor for a while but the model lock-in is starting to bother me. The 500+ models angle here is hard to ignore. Does switching models mid-project break any context?
Kilo Code
@alexis_rodriguez7 happy to hear, and no, you can even switch model mid task.
exactly - 500+ models, zero markup, no editor switch required. see full comparison vs Cursor here: kilo.ai/kilo-code/vs/cursor#comparison
hope this helps!
KiloClaw
@alexis_rodriguez7 It does not! You can switch in between prompts, or even run parallel agents using different models to see how they handle the tasks differently.
Your context remains intact!
Orbit
Been loving my experience with Kilo! Love the team and the speed at which things are shipped. This is just another great example of the speed at which this team can produce great work!
spot on! this team keeps shipping: @Kilo Code for @VS Code and @JetBrains, and more with @KiloClaw...
Kilo Code
@erik_israni Kilo Speed!
KiloClaw
@erik_israni Thank you! Glad you're enjoying it :)
Used the old Kilo VS extension and have been using the new. Love the changes and it works smoothly. Excited to see many of the coming updates, too.
amazing, Josh! what should we build/improve/fix from your perspective?? here's a sneak peek: kilo.ai/next
Kilo Code
@josh_slone1 thanks for joining us on the journey. What do you like most from the new version?
KiloClaw
@josh_slone1 Thank you! Glad you're enjoying it.