Please release v7.x as a new separate plugin, not an overwrite update—don’t force upgrade #8155
Replies: 4 comments
-
|
I kind of felt the same way, but if you click the gear on the plugins area you can just pick the previous version. Easypeasy, then if there's feature parity between the new one and the old one, you can just click the auto-update box again. |
Beta Was this translation helpful? Give feedback.
-
|
I totally agree! This new version is almost suffocating to use. |
Beta Was this translation helpful? Give feedback.
-
|
100% agree, new v7.x is awful :( |
Beta Was this translation helpful? Give feedback.
-
|
In version 7.*, 20-30 issues are added every day. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m a long-time KiloCode user and I’m extremely frustrated with the v7.x update.
Instead of releasing the new version as a completely separate plugin (so users can choose to install it or keep the old one), you forced an overwrite update that replaced the old, stable version entirely.
This is a huge problem:
I didn’t want to upgrade at all—my workflow relied entirely on the old Architect mode and the old UI/UX.
Now I have no choice but to use the broken v7.x, which is far less usable for architecture design and daily work.
The new Plan mode can’t replace Architect mode at all, and the new interaction is buggy, slow, and often stuck.
If you want to launch a new, simplified version, that’s fine—but don’t destroy the old one.
Please:
Release v7.x as a separate, optional plugin (e.g., “KiloCode New” or “KiloCode Lite”)
Let users keep the old stable plugin alongside the new one
Stop forcing everyone to upgrade to a version that breaks core functionality
This would respect both new users who want simplicity and long-time users who need the professional features of the old version.
Beta Was this translation helpful? Give feedback.
All reactions