fix(vscode): bundle local bwrap helper - #11657
Conversation
| const indexingEnv = resolveIndexingEnv(folders) | ||
| const localCli = | ||
| this.context.extensionMode === vscode.ExtensionMode.Development || | ||
| fs.existsSync(path.join(this.context.extensionPath, "bin", ".cli-version")) |
There was a problem hiding this comment.
WARNING: .cli-version will mark packaged installs as local too
prepare:cli-binary also runs for the package script, and .vscodeignore includes bin/**, so the marker written by local-bin.ts is shipped in the VSIX as well. That makes this branch true outside F5/dev sessions, so production installs can start injecting KILO_BWRAP_PATH from ~/.cache/kilo-vscode/bwrap whenever the bundled helper looks incomplete, which is broader than the local-only fallback this change is trying to add.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (5 files)
Reviewed by gpt-5.4-20260305 · Input: 143.8K · Output: 13.8K · Cached: 617.8K Review guidance: REVIEW.md from base branch |
…p-bundle fix(vscode): bundle local bwrap helper
Local source-wrapper VS Code dev launches run the CLI through Bun, so a Bubblewrap helper beside
bin/kilois not discovered throughprocess.execPath.This stages a verified Bubblewrap helper in the user cache and passes
KILO_BWRAP_PATHonly for local/dev CLI launches when a complete production helper is absent. Production bundled helpers and explicit userKILO_BWRAP_PATHoverrides keep their existing behavior.