fix(vscode): bootstrap dependencies in worktrees - #13265
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by grok-4.6 · Input: 239.8K · Output: 8.5K · Cached: 410.4K Review guidance: REVIEW.md from base branch |
marius-kilocode
enabled auto-merge
August 20, 2026 10:09
johnnyeric
approved these changes
Aug 20, 2026
This was referenced Aug 24, 2026
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.
Fresh Agent Manager worktrees do not contain ignored node_modules or generated build artifacts. Running the extension launcher in one of these worktrees therefore fails when Bun cannot resolve workspace packages such as @opencode-ai/core, even though the source checkout is valid.
The launcher now checks the required extension bundler, CLI core, and SDK generator modules before building. If any are missing, it runs one locked root workspace install with bun install --frozen-lockfile. Existing launches with valid dependencies continue without an install.
This keeps dependency provisioning at the launcher boundary, where it covers direct launch commands and Agent Manager run scripts without changing CLI or SDK build behavior.