Kilo Code's VS Code extension reaches week three of its post-GA update series, focusing on two major pain points: Windows memory usage and session stability. The Agent Manager's git work was moved to the extension host to fix multi-GB RAM growth on Windows, diff sizes are now capped, and the allocator was tuned to release memory more promptly. Session stability improvements address stuck states when VS Code closes mid-suggestion, broken end-of-plan transitions, and chat view scroll snapping during streaming. New features include session forking from any message, KiloClaw chat panel inside VS Code, folder @-mentions for context, and autocomplete backend prewarming. Three upstream OpenCode releases (v1.4.4–v1.4.6) were also merged. The team notes this is the last weekly update in the series, with core issues now resolved or significantly improved.

7m read timeFrom blog.kilo.ai
Post cover image
Table of contents
Windows Memory: A Big Step ForwardSession Stability: Fewer InterruptionsNew Capabilities This CycleUpstream OpenCodeCodebase Indexing ProgressCommunity UpdateMoving at Kilo Speed Into the Future

Sort: