Repository navigation
docs: add WSL disconnect diagnostics to troubleshooting guide - #14656
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Contributor
Author
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Previous Review Summary (commit 69a6a4d)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 69a6a4d)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
The added section is otherwise accurate: the Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
alexkgold
approved these changes
Sep 29, 2026
This was referenced Oct 7, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a "Diagnosing WSL disconnects" section to the existing Extension Troubleshooting page, based on this gist: https://gist.github.com/kirillk/1a50147ef0f39dc8948f9009d982ace3
Why
Users running Kilo Code with VS Code on WSL hit disconnects that are hard to diagnose after the fact — restarting WSL or rebooting wipes the evidence. This documents a single copy-paste command that captures a diagnostic bundle (kernel OOM events, WSL VM uptime, memory stats, VS Code remote server logs, and Kilo logs) to
C:\Users\Public\kilo-diag.tgzbefore restarting, plus a request for the number of parallel Agent Manager sessions/worktrees.Where
Integrated into the existing extension troubleshooting page (alongside the console-log capture and SQLite reset sections) rather than a new page, matching the docs' frontmatter, heading, numbered-step, and code-block conventions.
Verified with the kilo-docs vitest suite (4 files, 22 tests passing).
Built for Alex Gold by Kilo for Slack