github Kilo-Org/kilocode v7.2.17

pre-release8 hours ago

Minor Changes

  • #9207 4d85c23 - Support forking Agent Manager sessions from a specific user message.

  • #9244 18442f6 - Support forking sidebar conversations from any user message.

Patch Changes

  • #9305 b4cb8c3 - Prewarm the autocomplete backend on activation so inline completions are ready on first keystroke without opening the Kilo sidebar, and refresh autocomplete state when workspace folders change.

  • #9318 bfe4482 - Prevent canceled autocomplete debounce requests from staying pending indefinitely.

  • #9316 bf98bbe - Cap autocomplete ignore path caching so long sessions do not retain unlimited paths.

  • #9239 2b17a7b - Fix custom provider model and variant deletions being silently reverted on save. Removing a model or reasoning variant from a custom provider now actually removes it from your config.

  • #9241 6c0439b - Fix custom provider variant name validation showing inline errors correctly when a variant name is left empty

  • #9208 acd5798 - Fixed Agent Manager incorrectly duplicating worktree sessions into the Local tab when forking a session or using "Continue in Worktree".

  • #7960 d1aed36 - Add KiloClaw chat panel to the VS Code extension

  • #9245 ec5ac2e - Fix the "Continue here" button not submitting after a plan is finished. Picking an option on a single-question prompt now sends the reply immediately — matching the CLI behaviour — and the redundant "Type your own answer" row no longer appears on the plan follow-up question.

  • #9246 c529142 - Translate the follow-up prompt shown after finishing a plan. The "Ready to implement?" question, "Start new session" and "Continue here" buttons, and their descriptions now respect the language configured in the VS Code sidebar.

  • #9129 60709fd - Fix duplicate text shown when typing a custom answer in the question tool. The preview text above the input field is now hidden while editing, so only the input value is visible.

  • #9195 7038ce0 - Fix queued follow-up messages so they stay stacked at the bottom of the chat while the previous turn is still being processed, instead of getting interleaved with tool output.

  • #9194 0ace2f9 - Restore earlier chat history when scrolling through virtualized message lists.

  • #9236 6f17bb7 - Fix chat scroll jumping back to the bottom while the session is busy — you can now scroll up to read earlier context while a response is streaming or while a question is waiting for your answer.

  • #9199 7a1388d - Fix a stuck session state when the suggest tool was left open. If the suggestion was never accepted or dismissed (for example, because VS Code was closed while it was showing), the session stayed marked as busy and any follow-up messages appeared queued forever. The session is now marked idle while waiting for a response to a suggestion.

  • #9141 61ec925 - Restore spacing between sub-agent output and the following user message in the VS Code chat.

Don't miss a new kilocode release

NewReleases is sending notifications on new releases.