Last week, we GA’d the completely rebuilt Kilo Code extension for VS Code — the culmination of weeks of work bringing the same portable OpenCode server-based engine from the CLI into your editor.
I'd like to have the v5 branch continue developing. I like just nothing about the new Kilo. Switching to Cline and/or RooCode is a much simpler path for me then accepting all the disadvantages and limitations v7 brings in. I understand you guys that it's simpler to work on one codebase. But it feels like you think more about how it is easy for you than what you change for users. Kilo 5 and Kilo 7 VS Code extensions are two completely different tools. I see nothing common in them except the models, modes, and tokens. What if some of the users don't want to move from the product they initially chose?
Hey Blondie! What model are you using? In my own usage it is a lot faster since for the bigger prompts because it spins of multiple parallel subagents, and also does the tool calls in parallel
I love this software and I love how well the company responds to user feedback.
IF you are running into an issue where your session fails, using the new or legacy versions, make sure that you have both a .gitignore AND a .kiloignore file setup to EXCLUDE those folders or specific files. After that, everything works as you've come to expect.
The legacy version uses both Github (optionally) and a shadow GIT which allows mid-development rollback to a specific task/edit within that session. The new version only uses Git, so your rollback granularity is locked at the per-session level.
This is the only reason that so many of us haven't upgraded from legacy. Shadow GIT is a PITA to develop and maintain, so I understand the business case for it. Nonetheless, thank you to Kilo Code for allowing users to keep using the option that best fits their personal workflow needs!
I really like the new extension and all its features: LSP (Language Server Protocol), speed, subagents, and worktree. That's great! Also, I appreciate that you use AGENT.MD as the standard. Thank you for your hard work and for creating such a cool extension!
I also really enjoy using OpenCode and older Kilocode. They serve different purposes for me. I use Kilocode for more interactive development, and OpenCode is great for parallel implementation and testing. And I love that my two favorite agent systems are now coming together in Kilov7! I have already transitioned to the new way of working with agents and I love it!
I'd like to have the v5 branch continue developing. I like just nothing about the new Kilo. Switching to Cline and/or RooCode is a much simpler path for me then accepting all the disadvantages and limitations v7 brings in. I understand you guys that it's simpler to work on one codebase. But it feels like you think more about how it is easy for you than what you change for users. Kilo 5 and Kilo 7 VS Code extensions are two completely different tools. I see nothing common in them except the models, modes, and tokens. What if some of the users don't want to move from the product they initially chose?
You promised greater speed and instead we have extremely slowness and many bugs
Hey Blondie! What model are you using? In my own usage it is a lot faster since for the bigger prompts because it spins of multiple parallel subagents, and also does the tool calls in parallel
I'm using Sonnet 4.6 but without parallel subagents
Switching back is an option for the time being, but I'm pretty sure it won't be maintained. Please prove me wrong.
I love this software and I love how well the company responds to user feedback.
IF you are running into an issue where your session fails, using the new or legacy versions, make sure that you have both a .gitignore AND a .kiloignore file setup to EXCLUDE those folders or specific files. After that, everything works as you've come to expect.
The legacy version uses both Github (optionally) and a shadow GIT which allows mid-development rollback to a specific task/edit within that session. The new version only uses Git, so your rollback granularity is locked at the per-session level.
This is the only reason that so many of us haven't upgraded from legacy. Shadow GIT is a PITA to develop and maintain, so I understand the business case for it. Nonetheless, thank you to Kilo Code for allowing users to keep using the option that best fits their personal workflow needs!
I really like the new extension and all its features: LSP (Language Server Protocol), speed, subagents, and worktree. That's great! Also, I appreciate that you use AGENT.MD as the standard. Thank you for your hard work and for creating such a cool extension!
I also really enjoy using OpenCode and older Kilocode. They serve different purposes for me. I use Kilocode for more interactive development, and OpenCode is great for parallel implementation and testing. And I love that my two favorite agent systems are now coming together in Kilov7! I have already transitioned to the new way of working with agents and I love it!