Windows Terminal setup doesn't work in WSL

[qwaz]

Describe the bug

Copilot CLI running in Windows Terminal/WSL refuses to setup Windows Terminal.
✗ No supported terminal detected. `/terminal-setup` is supported only in VS Code, Cursor, Windsurf and Windows Terminal.

The WSL Ubuntu distro automatically sets TERM=xterm-256color. I expect this is somehow related.

The keybinding is installed to the Windows Terminal profile, and if I install the keybinding on Windows Terminal + Powershell, that also fixes the problem in Windows Terminal + WSL. However, it would be great if it works automatically inside Windows Terminal + WSL.

Affected version

GitHub Copilot CLI: 1.0.36 / Windows Terminal: 1.24.10921.0 / WSL Distro: Ubuntu 24.04.4 LTS

Steps to reproduce the behavior

Run /terminal-setup inside Copilot, running in WSL distro on Windows Terminal

Expected behavior

Windows terminal is setup to send correct key sequence for shift + enter.

Additional context

No response

[tpope]

It's not related to TERM. It needs to alter the local settings.json for Windows Terminal. That's not part of your VM.

We could maybe get this to work through /mnt/, but I imagine that would be fraught with edge cases. Since the next stable release (and current pre-release) of Windows Terminal is going to support shift+enter natively, rendering /terminal-setup obsolete, I don't expect we'll be pursuing this.

Edit: Detecting Windows Terminal happens via WT_SESSION, which would be a second hurdle to overcome.