Feature request
When the active terminal is a WSL distro (e.g. Ubuntu) and the agent decides it needs to launch a new terminal, it should open a new terminal of the same kind (WSL/Ubuntu), not fall back to the user''s default profile (e.g. PowerShell).
Current behavior
If the active pane is Ubuntu and the agent spawns a new terminal, it uses the default profile (PowerShell) instead of a new Ubuntu terminal.
Expected
The newly launched terminal should match the active session''s shell/profile (WSL distro) so the agent''s follow-up commands run in the right environment.
Origin
Raised by @dot-mike on #200:
Also seeing another bug similar to this. I.e if the active terminal is Ubuntu, and the agent decides it needs to launch a new terminal, it will use the default terminal (for example Powershell) and not a new Ubuntu terminal.
#200 (comment)
Related
Feature request
When the active terminal is a WSL distro (e.g. Ubuntu) and the agent decides it needs to launch a new terminal, it should open a new terminal of the same kind (WSL/Ubuntu), not fall back to the user''s default profile (e.g. PowerShell).
Current behavior
If the active pane is Ubuntu and the agent spawns a new terminal, it uses the default profile (PowerShell) instead of a new Ubuntu terminal.
Expected
The newly launched terminal should match the active session''s shell/profile (WSL distro) so the agent''s follow-up commands run in the right environment.
Origin
Raised by @dot-mike on #200:
#200 (comment)
Related
OSC 9001;ShellType, PR feat(shell): self-report shell identity via OSC 9001;ShellType #345), which only covers reading the current pane''s shell, not which profile a new terminal opens with.