Skip to content

docs(kilo-docs): clarify VS Code extension local launch #11663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johnnyeric merged 3 commits into from
Jun 30, 2026
Merged

docs(kilo-docs): clarify VS Code extension local launch #11663

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f92e9a6
docs(kilo-docs): document VS Code extension local launch
singhvishalkr Jun 24, 2026
a6dbc0f
docs(kilo-docs): add Windows extension env example
singhvishalkr Jun 24, 2026
ae48705
Merge branch 'main' into docs/vscode-extension-local-dev
johnnyeric Jun 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions packages/kilo-docs/pages/contributing/development-environment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,25 @@ bun run extension

This will build and launch the extension in an isolated VS Code instance.

The command auto-detects VS Code on macOS, Linux, and Windows. Use these options when the default launch target is not the one you need:

| Option | Use |
|---|---|
| `--no-build` | Launch the extension host without rebuilding first |
| `--app-path <path>` | Point to a specific VS Code executable |
| `VSCODE_EXEC_PATH=<path>` | Set the VS Code executable through the environment |

@kilo-code-bot kilo-code-bot Bot Jun 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: POSIX-only environment syntax in a cross-platform docs table

VSCODE_EXEC_PATH=<path> is shell-assignment syntax that works in bash/zsh, but not in PowerShell or cmd.exe. Because this section explicitly calls out Windows support, a Windows contributor copying this row can end up with a failing command. Could we either describe this as the env var name only, like CONTRIBUTING.md, or add the Windows form separately?

Suggested change
| `VSCODE_EXEC_PATH=<path>` | Set the VS Code executable through the environment |
| `VSCODE_EXEC_PATH` | Set the VS Code executable through the environment |

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

| `--insiders` | Prefer VS Code Insiders |
| `--workspace <path>` | Open a specific workspace folder |
| `--clean` | Reset cached extension state before launch |

For example, to test the extension against a sample workspace:

```bash
bun run extension --workspace ../sample-project
```

When the Extension Development Host opens, check the Kilo Code output channel and the Developer Tools console for startup or webview errors.

### Building the Extension

From `packages/kilo-vscode/`:
Expand Down
Loading