microsoft / microsoft/vscode

Agent-created worktree sessions default to Local and disappear

Open
#335,825 0 comments 1 reaction 2 assignees Claimed by @meganrogge View on GitHub
bug voice-mode
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

### Type of issue

Bug

### Description

When asking Copilot in a normal VS Code window to create worktrees and do work in them, the newly created sessions are assigned to **Local** rather than the current workspace when using voice mode. They do not appear to retain awareness of the workspace, and after creation the session can disappear from the expected session list.

### Steps to reproduce

1. Open a workspace in the normal VS Code window.
2. Ask Copilot to create one or more worktrees and perform work in them using voice mode
3. Observe the newly created agent sessions.

### Expected behavior

The sessions remain associated with the originating workspace/worktrees and remain visible in the expected session list.

### Actual behavior

The sessions are created under **Local**, appear not to know about the originating workspace, and can vanish after creation. Instead, the sessions should use whatever harness is selected or default to **Copilot**.

Reported by @jamesmontemagno in Slack with a screen recording.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.