Open in Editor opens the wrong workspace folder for WSL agent sessions

@benvillalobos is already working on this.

Since Sep 19, 2026.

- Copilot Chat Extension Version: Not available from the WSL CLI
- VS Code Version: 1.138.0 (7debcd0e2acdea1c52de81bf9ee1620444407dda, x64)
- OS Version: Windows NT 10.0.26200.0; WSL2 kernel 5.15.167.4; Ubuntu 24.04.1 LTS
- Feature: Copilot agent sessions / Open in Editor
- Selected model: N/A
- Logs: No error is shown; the editor opens with the wrong workspace folder

Steps to Reproduce:

1. Open a folder in a WSL remote window.
2. Start or resume a Copilot agent session associated with that WSL folder.
3. From the session UI, click **Open in Editor**.
4. Observe the workspace folder opened by the editor.

**Expected behavior**

VS Code should open the folder associated with the agent session in a WSL remote editor window, preserving both the WSL remote authority/distro and the exact Linux path (for example, `vscode-remote://wsl+Ubuntu/home/boren/code/`).

**Actual behavior**

The editor does open, but it does not open the correct work folder for the WSL session. This makes **Open in Editor** unreliable because the resulting editor is not attached to the workspace where the agent session is running.

This is specifically about navigating **from an existing WSL agent session to the editor**. It is the reverse direction from the older **Open in Agents** WSL issue (#316342).

Does this issue occur when all extensions are disabled?: Not tested; the affected action is part of the Copilot agent-session integration.