Summary
Worktree items in the Commit Graph sidebar and the Worktrees view offer no way to open the worktree's folder in VS Code's integrated terminal — even though repositories and folders already do.
Impact
Anyone juggling multiple worktrees who wants a terminal rooted at a specific worktree. Today they have to reveal the worktree in the file explorer and open a terminal by hand, or open the worktree as a workspace first. Since repositories and folders already expose "Open in Integrated Terminal," worktrees are an inconsistent gap.
Validation
- Open a repo that has at least one secondary worktree.
- In the Commit Graph, expand the worktrees in the sidebar, right-click a worktree → Open in Integrated Terminal; confirm a terminal opens at that worktree's folder (not the main repo).
- In the Worktrees view, right-click a worktree node → Open in Integrated Terminal; confirm the same.
- In a remote-dev session (SSH / vscode.dev), confirm the terminal opens at the correct worktree path.
Risk
Low — builds on the integrated-terminal action already available for repositories and folders, and existing behavior is unchanged. The action is hidden in virtual workspaces where no terminal is available.
Summary
Worktree items in the Commit Graph sidebar and the Worktrees view offer no way to open the worktree's folder in VS Code's integrated terminal — even though repositories and folders already do.
Impact
Anyone juggling multiple worktrees who wants a terminal rooted at a specific worktree. Today they have to reveal the worktree in the file explorer and open a terminal by hand, or open the worktree as a workspace first. Since repositories and folders already expose "Open in Integrated Terminal," worktrees are an inconsistent gap.
Validation
Risk
Low — builds on the integrated-terminal action already available for repositories and folders, and existing behavior is unchanged. The action is hidden in virtual workspaces where no terminal is available.