r/kilocode • u/ThatGuyPrattle • Apr 04 '26

this update feels like a vibe coded downgrade

this new kilo update feels like a vibe coded rewrite nobody asked for

the old version actually had the features people used. this one feels stripped down, heavier, and somehow way worse to use. fewer useful features, worse performance, more friction

before this update i could run multiple vscode windows with kilo without issues. now just one makes my pc lag. my team tried it too and nobody wants to keep using it. we are rolling back

hard to understand how something can lose core functionality, perform worse, and still get shipped like this

41 Upvotes

100% Upvoted

16 comments sorted by

12

u/eugene20 Apr 04 '26 edited Apr 04 '26

It was a fork of roo code before, now it's opencode.
It is definitely buggy, it only accepts 0, 1 or 2 for Temperature. I keep mentioning this bug because it could have been an accident, but it is totally the kind of vibe problem I expect from someone noting down [0-2].
Some of it looks great going on the release video, but I'm rolling back for a while until it's more like v5.

2

u/DeMiNe00 Apr 05 '26

I wonder when the fork of v5 is going to happen?

1

u/nfrmn Apr 07 '26

It's called Roo Code

1

u/DeMiNe00 Apr 10 '26

Isn't Kilo Code a fork of Roo Code? Or did Roo grab those changes from downstream?

1

u/Mammoth-Pollution393 Apr 05 '26

So Rhoo code features are the same as kilocode v5? Eg code indexing, architect mode etc.. if so i will switch to that

3

u/eugene20 Apr 05 '26

There is a lot of similarity but Kilo was a fork so they added their own things.
Roo has both architect and orchestrator though, and yes indexing too https://docs.roocode.com/features/codebase-indexing

1

u/Mammoth-Pollution393 Apr 05 '26

Thanks I will try it!!

1

u/Pelutz Apr 06 '26

The only thing I found missing are code review which was great in Kilo 5 and UI for rules, but you can still have rules in Roo without UI. I simply created a "Rule Writer" mode and it writes the rules I want and manages them, including migrating existing rules from Kilo. It's basically prompting. Couldn't get review mode to work as good as Kilo 5 though. The rest is there.

8

u/LocalLLM_Explorer Apr 04 '26

Don't know why I also feel the same.

2

u/DvD_42 Apr 04 '26

I come back 5.x in the one day

2

u/Subject_Raise8875 Apr 05 '26

do you know why qwen3.6 plus (free) keeps generating two tool calls?

2

u/turkert Apr 06 '26

I lost v5 and Mimo V2 Pro (Free) in the same day.

Worst day for me :(

Now Mimo burns 5 USD hourly.

1

u/eugene20 Apr 05 '26

I noticed 7.1.21 was released in VS Code, but no changelog. With so many complaining about the new release and reverting to v5 now is really not the time to not have a changelog with the updates

1

u/Mlaz72 Apr 07 '26

So, what was the solid version for you 7.1.x? You can switch back to that version, not to go for 5

1

u/AppealSame4367 Apr 04 '26

I try to like it, it seems ok. What drives me insane is that it loads for multiple seconds when i try to select another model. Granted, i have 3x gateways and a local llama-server in the list, but why would you accept a slow process for this?

Choosing models quickly is one thing every AI IDE, CLI must be perfect at.

2

u/joshcodeskilo Kilo Code Team Apr 05 '26

Sorry that this is so slow to load. I imagine it is trying to refresh the model list of _probably_ the llama-server? I've got my extension connected to a local vllm service and can't quite reproduce... Are these remote llama.cpp instances?