Tracking: first-class WSL session support for the agent

[vanzue]

Feature request — WSL session support (tracking)

Umbrella tracking issue for making WSL terminals/sessions first-class for the agent: detection, context enrichment, command insert/run, and new-terminal launch all behaving correctly when the active session is a WSL distro.

#200 is currently filed as a single bug but actually bundles several distinct problems; this issue tracks the WSL-session story so the pieces can be tracked independently.

Sub-parts

• Shell-context awareness — a WSL shell pane self-reports its identity (wsl:<distro>) so the agent suggests bash syntax instead of PowerShell. (Done via OSC 9001;ShellType; see PR feat(shell): self-report shell identity via OSC 9001;ShellType #345.)
• Insert/Run into a WSL pane fails with 0x80010105 The server threw an exception (the COM send-input path). Reported on Support WSL terminals #200.
• Agent-launched new terminal uses the default profile (PowerShell) instead of a new WSL/Ubuntu terminal when the active pane is WSL — tracked separately (see linked feature issue).
• ACP agent running inside WSL as an agent-pane backend — tracked separately (Support ACP agents running inside WSL as an agent-pane backend (Copilot/OpenCode/CodeX) #349).

Origin

Filed to give the WSL work a trackable home, splitting out of #200.

Related

• Support WSL terminals #200 (original bug report — Support WSL terminals)
• Support ACP agents running inside WSL as an agent-pane backend (Copilot/OpenCode/CodeX) #349 (ACP agent inside WSL)