Add troubleshooting with console capture#5865
Conversation
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Code Review SummaryStatus: No New Issues Found | Recommendation: Address existing comments before merge OverviewThis PR adds a troubleshooting section to the Kilo Code documentation under Previous review rounds have already identified the key issues — no additional problems found in this pass. Previously Flagged Issues (from other reviewers)
Key items still worth addressing:
Files Reviewed (4 files)
|
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
|
Seems like this is geared towards the extension so maybe make that clear / organize a troubleshooting folder with just one in it for now for the extension. |
Review: kilocode #5865
Checklist
Findings🟡 Page not added to navigationThe troubleshooting page is created at Suggested fix: Add to the "Help" section in {
title: "Help",
links: [
{ href: "/getting-started/faq", children: "FAQ" },
{ href: "/getting-started/troubleshooting", children: "Troubleshooting" },
{
href: "/getting-started/migrating",
children: "Migrating from Cursor",
},
],
},🟡 Maintainer feedback: scope and organization@olearycrew commented that this guide is geared towards the extension and suggested:
This feedback should be addressed before merge. ⚪ JetBrains instructions could be simplerThe JetBrains section asks users to enable
CI Status
Code Snippets# New file: apps/kilocode-docs/pages/getting-started/troubleshooting.md
## Opening Developer Tools
{% tabs %}
{% tab label="VS Code" %}
1. **Open the Command Palette**: Press `Ctrl+Shift+P` (Windows/Linux) or `Cmd+Shift+P` (Mac)
2. **Search for Developer Tools**: Type `Developer: Open Webview Developer Tools` and select it
{% /tab %}
{% tab label="JetBrains" %}
### Enable JCEF Debugging
1. Go to Help → Find Action → Registry
2. Set `ide.browser.jcef.debug.port` → `9222`
3. Enable `ide.browser.jcef.contextMenu.devTools.enabled`
4. Restart IDE
### Connect Chrome DevTools
1. Navigate to `http://localhost:9222/json`
2. Find entry with `"title": "Kilo Code"`, open `devtoolsFrontendUrl`
{% /tab %}
{% /tabs %}VerdictCOMMENT - Well-written troubleshooting guide with good Markdoc tabs usage. Two items need attention before merge: (1) the page must be added to the nav config in |
Review Journal: kilocode #5865
SummaryA new troubleshooting guide for capturing console logs in VS Code and JetBrains IDEs. Well-written content with proper Markdoc tab components, but the page isn't connected to the site navigation and maintainer @olearycrew has unaddressed feedback about scope and organization. Needs nav integration and maintainer alignment before merge. First ImpressionsTitle "Add troubleshooting with console capture" signals a practical support doc. At 58 lines in a single new file, this is a clean addition — no existing code modified. The PR description is minimal ("let me know if you have any thoughts/feedback"), suggesting early-stage content seeking review. What I Looked At
AnalysisContent quality is solidThe guide covers two IDEs with appropriate tabs: VS Code (3 steps): Command Palette → Developer: Open Webview Developer Tools → Console tab. Straightforward and accurate. JetBrains (2 sections):
The "Capturing the Error" section and "Contact Support" section are clean and actionable. Missing navigation integrationThe page is created but { href: "/getting-started/faq", children: "FAQ" },
{ href: "/getting-started/migrating", children: "Migrating from Cursor" },A Maintainer feedback not yet addressed@olearycrew commented:
Two requests:
JetBrains UX could be simplerThe instructions enable the context menu DevTools (
VerificationAll CI checks pass (this is the first external-contributor PR where Vercel also passed): Bot Review Synthesis
Greptile investigation needed: Greptile has not commented on any of our 4 fork PRs despite being installed and configured with a detailed Lessons Learned1. New pages need nav integration. Creating a page without updating the nav config is a common oversight in docs PRs. This should be a standard checklist item: "If adding a new page, is it linked from the nav?" 2. Maintainer feedback is part of the review. @olearycrew's comments on scope and folder organization represent design decisions that should be resolved before a code review can give a final verdict. Our review acknowledges and surfaces this feedback. 3. Vercel deploys for some external contributors. Unlike PR #5667 where Vercel skipped, this PR's author (@alexkgold) has auth to trigger Vercel deploys. This means they likely have org access — different from truly external contributors. 4. Greptile remains non-functional. 0/4 PRs reviewed despite proper config. This needs to be resolved for the tool to earn its $20/month. All the value so far comes from CodeRabbit (free) and Gemini (free). Review #4 of 75 | Review methodology: AI PR Review Case Studies | Reviewed with GWI + Claude Code |
Mirror: Add troubleshooting with console capture (Kilo-Org#5865)
olearycrew
left a comment
olearycrew
left a comment
There was a problem hiding this comment.
@alexkgold approved but see my note
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
…leshooting-extension.md Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Add troubleshooting with console capture
5 participants
@LigiaZ -- let me know if you have any thoguhts/feedback
@olearycrew -- is this the right place?