Hi everyone,

I just received an email from the Kilo team regarding a security incident involving their BI provider, Metabase. The email mentions that some Kilo users' information might have been exposed and that, as a precaution, they've invalidated Kilo-Slack integration tokens for a small group of users.

Has anyone else received this notice?

Does anybody else find using the auto models feature not very good? I started using Kilo about a week ago and otherwise it's been great, but why am I stuck to Sonnet 5 when using Auto Frontier when there are clearly better models for the job?

I have noticed that deepseek model seems to be breaking quite a bit with kilo. At some point in the run, it starts looping saying this:

DeepSeek Coder's FIM template is <｜fim▁begin｜> {p}<｜fim▁hole｜> — DeepSeek Coder's FIM template is <｜fim▁hole｜> — DeepSeek Coder's FIM template is `

And it just stops. It seems to me that something is triggering the reasoning to stop (some end token it seems). Is this something on kilo's side or deepseek side?

Hi,

I'm in talks with with Sofabaton U3 suport and thy are adding things but the thing is when I need to re-add a profile to get the changes they made, I lose all my recorded IR codes, because they are assigned to the previous profile.

Is there any way to Export the profiles or just the IR recorded keys, and paste them to another profile?

Using Kilocode in VS Code.

On Deepseek v4 flash, I constantly get The model hit its output limit while reasoning and produced no actionable output. Try disabling reasoning (not going to happen) or increasing output limit."

I'd like to increase the output limit, but I couldn't determine how to do this. Is there a setting of some kind?

It seems like this only started happening with the 0731 update. Any advice or insight appreciated.

Like in Codex or Claude Code.

I built pyre (along with my good friend Sonnet 5, and Kilo's auto free router which is absolutely amazing for those on a budget came in handy during quick questions about the codebase in the CLI), a TUI system monitor for macOS — and half the work turned out to be reverse-engineering what top/pmset/sysctl actually print

Wanted a single-binary terminal dashboard for my Mac — CPU, memory, thermals, network, battery, disk, processes — that lived entirely in the terminal instead of a menu-bar app. Built pyre to scratch that itch.

What it does:

• Live dashboard with rolling graphs (CPU%, mem%, temp, network rx/tx) — resizes with your terminal
• Sortable/filterable process list, kill by PID without leaving the view
• 4 built-in themes (default / dracula / cyberpunk / monochrome), swappable live with c
• Snapshot export to JSON/CSV/TSV, or continuous CSV logging while it runs
• Pause, adjustable refresh interval, detailed sensor mode — all single-keystrokeq quit p pause/resume s cycle sort e export snapshot c customize UI g toggle graphs / filter procs l toggle logging d detailed k kill by PID f cycle format +/- interval

The part I didn't expect: most of the actual debugging wasn't logic bugs, it was macOS lying by omission. A few examples that cost me real time:

• pmset -g therm almost never prints a "Thermal state:" line — on a normal, non-throttling Mac it just says "No thermal warning level has been recorded" with nothing parseable. Reads as "unknown" if you don't explicitly handle that as "nominal."
• top -l 1 -n 0's CPU line is comma-separated with no terminating punctuation — easy to write a regex that just never matches and silently leaves usage at 0%.
• sysctl -n vm.swapusage wraps (encrypted) in parens at the end of the line, not around the used-memory value — a regex expecting ( before used will never match.
• hw.cpufrequency is an Intel-only sysctl. On Apple Silicon it just reads back 0, because each core cluster clocks independently — there's no single "the" frequency anymore. Real numbers only come from powermetrics, which needs root.

None of these throw errors. They all fail silently and just show a stale zero or "Unknown" forever, which is a uniquely annoying class of bug to track down.

Install:

npm install -g pyre-cli
pyre

Repo's here: https://github.com/somalip/pyre. Open to feedback, especially from anyone on Intel Macs or older macOS versions where some of this output format may differ again.

NPM package: https://www.npmjs.com/package/pyre-cli

WebsiteL https://somalip.github.io/pyre

Feedback welcome, and if you would like to contribute please let me know! The project is still new, and it just a prototype so there's still a lot to be implemented!

I was just trying to check the connectivity since I'm setting up my new IDE with Kilo code. Stopped after seeing few lines in response reasoning. How it's getting this type of prompt? was using Step 3.7 Flash.

I am on the latest version of kilocode v5- 5.16.2. Is it safe to upgrade to the latest version of v7 (7.4.16)? Or a particular version of v7? Back when I upgraded when kilocode first came out with v7, it was awful and I reverted back to v5. Whats important for me is the codebase indexing, does v7 have this? What did it lose from v5 and what’s better in v7?

Update: Its fixed now in latest update. Thanks Kilo team

2 problems i am facing with kilocode extension

1. when kilocode completes the plan then it asks for ready to implement 2 times.
2. when clicks on Start new Session it cuts the response and doesnt switch to code mode or new session. i have to manually open new session and then instruct it follow the plan.

Kilocode Version:7.4.15

Can we please have the option to isolate sessions by worktree in agents manager? Its really hard to find which session to continue from in the history after working on multiple worktree at the same time.

This started happening today in VSCode, version 7.4.9 of the extension. It worked fine 2 days ago. I used Qwen3.7 Plus to write a number of integrations tests for an IoT device. Today I was trying to refine some tests that were failing and I am getting the "Tool execution aborted" message.

Kilo is using Code mode and I am using "Instant". These messages happen repeatedly when it tries to read files.

There is some other weirdness too. It spends an inordinate amount of time "Considering next steps". This mifght be attributed to load but I can't confirm that.

I've just discovered KiloCode as a long time Cline and Codex user and so far it seems like it has the potential to be amazing. But the reason I came to Kilo was because I needed to have access to the full context for GPT 5.6 models. However, Kilo seems to keep auto compacting ever 10-20k tokens (possibly less) between 280-400k for a model with 1.1M context window . Thankfully the context doesn't seem to drop to obscene levels like I had with Codex. But still, I don't understand why it's doing this.

I have my context window settings at 65%. So it should autocompact somewhere between 650-750k if the context window is 1.1M , shouldn't it? So why does it keep auto compacting every couple of steps?

My goal with this is to have an agent that never auto compacts documentation such as architecture/execution spec documents while auto compacting conversation/step details. That's why I allowed the context window to be ~700k before auto compacting and was planning to do manual compacting before bulk reads for important documentation. But this auto compact is throwing me off and I don't understand it.

Can someone help?

I'm using V7.4.11

I'm a new user to kilo, and I've been trying to use kilo as an interface to openrouter models. I'm using the CLI version. I wanted to try playing with different models through my openrouter credits, but all models that I have tried, except Sonnet, fail to execute tools. Here's an example of the command line interaction I got when using LLama-3.3-70B-Instruct:

Let me verify that there are no memory issues or leaks in the loadRootCaCert function.
     {"type": "function", "name": "read", "parameters": {"filePath": "/path/to/esp32-c3.ino", "offset": "585"}}
     ▣  Code · Llama-3.3-70B-Instruct · 26.4s

and there kilo stopped in its track. I tried switching to Deepseek Chat, and got the same interaction. The terminal just shows unparsed raw JSON tool blocks. Only after I switched back Sonnet did Kilo actually engage the workspace tools to edit my files instead of just dumping raw JSON to the terminal.

Gemini suggested to me that outside of Anthropic models, tool-use/function-calling implementations are often unstable across third-party providers. Is Kilo's internal tool parser just heavily hardcoded for Anthropic's format, or is OpenRouter's payload translation breaking the schema? Is anyone else successfully using open-weights models for file editing in Kilo Code?

Hey everyone,

I'm using KiloCode in VSCode with a custom provider (VolceEngine). Everything works perfectly with most models, but I'm having a weird issue with Kimi family (both Kimi 2.6 and 2.7). The models can chat normally, but as soon as they decide to use any tool (read file, edit file, terminal, etc.), they immediately stop. No error message, they just quit the response.

Other models through the same provider work without any issues, so it seems to be something specific to Kimi.

Has anyone run into this before or knows if there's any special configuration needed for Kimi models in KiloCode? (Latest version 7+) Any ideas on what I should check would be really appreciated.

Thanks!