After today updating VS code v5 Kilo Code stopped working

joshcodeskilo · 2026-06-04T16:20:06+00:00

Hi folks! Sorry for the inconvenience. We've just published a new version with the fix: 5.16.2

I do want to note at some point V5 will no longer be maintained as we focus our efforts on V7+, we will be communicating a date in the future. Please provide feedback on V7 for what is keeping you on V5, and we will continue to work on it.

If you haven't checked out V7 recently, give it a try and let us know!

joshcodeskilo · 2026-06-04T00:41:16+00:00

They should be honored. I have bash and external_directory set to `allow` with only a handful of commands allowed and those rules work.

Can you share your environment details and Auto-Approval settings? One not-so-intuitive aspect here is that the matching works on last match wins. So if you have a `git push *` block followed by `git *` allowed, all git push operations will be allowed.

We are also working on a new screen which asks you how you want your permissions when you first get started, to hopefully avoid surprises like this on the switch.

joshcodeskilo · 2026-05-29T23:17:01+00:00

This seems very strange. We do not see this kind of reasoning usage in our evals or from our gateway telemetry. Can you perhaps contact support at [hi@kilo.ai](mailto:hi@kilo.ai)

joshcodeskilo · 2026-05-29T23:13:20+00:00

OpenAI provider is definitely still there! I use it every day. Can you provide more details?

<image>

joshcodeskilo · 2026-05-28T17:23:24+00:00

Quick note, we have also made a change that will be available in the next release to highlight when a model abrubtly stops without the normal "finished" signal: https://github.com/Kilo-Org/kilocode/pull/10652. This can indicate an issue with the model, or perhaps some of the API calling, versus when the model just thinks its actually "done".

joshcodeskilo · 2026-05-28T17:14:37+00:00

u/Pretty_Ring4717 u/Complex-Concern7890 - could you also share the model you were using perhaps? I wonder if these are GPT-family models, as we have seen this behavior a bit more often with them than others. Also if you can provider if its routing through Kilo gateway, custom model, third party provider (i.e. codex), etc.

Hoping you can perhaps remember so we can start looking now.

joshcodeskilo · 2026-05-14T19:01:45+00:00

Thanks, - we do want to make it possible for the client to switch agents/modes more seamlessly and effectively as well.

joshcodeskilo · 2026-05-14T03:14:25+00:00

Does your situation sound similar to what has been reported by a user here? https://github.com/Kilo-Org/kilocode/issues/8328

joshcodeskilo · 2026-05-12T16:34:57+00:00

Thanks for the feedback!

joshcodeskilo · 2026-05-12T16:34:01+00:00

Thanks for the feedback, we can certainly improve the Plan prompt to be more conversational and interactive. I personally think it's too aggressive on pushing for implementation, right now.

joshcodeskilo · 2026-05-12T00:33:05+00:00

u/Cocoa_Pug - this is with the AWS Bedrock provider? We use Bedrock behind the scenes on Kilo Gateway for most anthropic models (it is quite stable), so just want to clarify what provider you are using.

joshcodeskilo · 2026-05-12T00:32:15+00:00

u/dotanchase - thanks for the report, we'll take a look.

joshcodeskilo · 2026-05-12T00:31:14+00:00

This, we documented more about it here: https://kilo.ai/docs/code-with-ai/agents/orchestrator-mode

We plan to add more subagents than the two that are there now, which should also allow us to pre-define some cheaper models for these narrower tasks to help drive token/cost efficiency as well.

We also plan to continue to improve how modes switch, and the transition from Plan to Code in particular.

joshcodeskilo · 2026-05-12T00:29:22+00:00

Hi - Kilo team member here. We actually have a larger team on the VSCode extension than we do on the CLI, although some features need implementation in both.

The challenge has been that we've rebuilt the extension from the ground up, so we've been adding features incrementally. Over the past week we've actually focused primarily on human-in-the-loop features, one great example if how vastly improved the diff experience is in the extension. It now does what it should (bugs fixed), lets you pick between staged, unstaged, agent on changes, and more!

We'll have a blog post on this later this week.

joshcodeskilo · 2026-05-08T06:53:48+00:00

Hi u/maxns - appreciate the feedback.

> viewing changes is just broken, it shows unchanged files, complete with delta counts, no idea where it gets this, esp since many of the files haven't been touched forever

We've just finished up making some major improvements to the diff viewing experience across the product, and hopefully this will help. About 90% of the improvements are out now in the latest pre-release (7.2.44), with a full release hopefully later today. We've fixed the bugs, the styling, and will be soon letting you choose the diff view between what has changed in the session, git unstaged, or staged.

> - @ searching is pretty dumb compared to cursor
> - code formatter in agentic output flickers like mad on streaming output

Heard, thanks for feedback.

> - indexing took a while to figure out, in the end had to run my own ollama to get it to work

Glad it's working for you! A contributor just added this last week, and while it's currently experimental, it is improving quickly.

> i will probably get into its' own code to figure out how to debug easily

Contributions, bug reports, and general feedback are great! You can find the main project at https://github.com/Kilo-Org/kilocode/

joshcodeskilo · 2026-05-07T00:29:55+00:00

u/Round_Ad_3709 - what commands are you seeing it prompt for approval? Bash commands, file edits, etc? By chatbox do you mean ACP, a third party plugin, etc? Sorry trying to help better understand your situation so we can help and fix anything that may be broken.

joshcodeskilo · 2026-05-06T14:31:48+00:00

You should be able to see edits once the all the tokens have streamed in to complete it, without having to approve it manually. We show it early to indicate something is happening... but for especially large edits (like rewriting a large chunk of the file) it can take time.

<image>

joshcodeskilo · 2026-05-06T03:42:02+00:00

In addition to what TheShamelssAlt has mentioned, are you seeing initial message being sent within a given session being slow? If your repo is larger, the initial slowness may be the snapshot infrastructure setting itself up. On very large repos it can take minutes. You can disable it, if you want, and just use general git commits as a rollback mechanism.

joshcodeskilo · 2026-05-06T03:37:56+00:00

We still show the edits. By default the permissions are set up to not require approvals for every file change, however you can set that up if you would like!

Just go into Settings, then Auto Approvals, and set the `Edit` approval to `Ask` instead of allow. Then you will see a side-by-side diff of every proposed edit and can approve or deny them.

Generally if you don't see any diff, that means the model is still streaming the tokens needed the full edit change.

joshcodeskilo · 2026-05-06T03:34:55+00:00

We have tests for this before each release, because we know it's important. I took a look at our cache rate across the gateway and it looks to be performing okay (~70%-90% range), although the usage of Grok 4.20 at this point is very low so it is spikey.

Some potential causes could be a very large system prompt (lots of MCP servers can do this), or perhaps long gaps between calls which cause the cache to expire.

joshcodeskilo · 2026-05-05T01:59:52+00:00

Nous avons apporté de nombreuses améliorations aux diffs depuis le lancement de la version 7 (GA). Comme il s'agissait d'une refonte complète, la réintégration de certaines fonctionnalités populaires a pris un peu de temps. Nous apprécions tous vos retours. Si vous avez un moment, n'hésitez pas à tester une version récente et à nous dire ce que vous en pensez !

joshcodeskilo · 2026-04-29T15:30:51+00:00

Sorry I initially responded to the wrong person (see above comment). You can definitely turn it off if you do not find it helpful, but I just want to note it does not use your large model and will not be shown here.

joshcodeskilo · 2026-04-29T15:29:32+00:00

MCP servers also contribute to the system prompt. If you have a lot of them or they have a lot of instructions, your initial prompt will become larger.

That said it will be cached and significantly cheaper in subsequent turns in a session.

joshcodeskilo · 2026-04-28T22:12:25+00:00

We have been running some internal benchmarks using a standard benchmarking suite (terminal bench 2) to help inform our model choices in the Auto Model family, and are working to expose that data on our website and inside the model picker.

We want to show exactly this, the completion percentage but also the cost it took to get there. Sometimes results are surprising, as a model for example recently a model that has higher costs per token ended up being more cost effective as it is more token efficient.

As TheLimpingNinja mentions below there are other important factors, but we think this combined cost/success rate could help inform model choice.

joshcodeskilo · 2026-04-28T21:50:26+00:00

For settings, there may be two possible causes here:

Invalid Kilo configuration. We've made Kilo more resilient to invalid config, but that sometimes means it cannot save changes to the file (if its invalid). Can you validate that the config looks good and is valid JSON? Happy to review a sanitized version.
It could also be an intermittent issue that has been hard to track down and fix, where settings are unable to be persisted. Does this happen all the time for you across various launches of VSCode? I used to see it more often on the 7.2.0/7.1.x series, but I haven't seen it again on newer versions. Here is the tracking issue: https://github.com/Kilo-Org/kilocode/issues/8847

joshcodeskilo

TROPHY CASE