FEAT: support WSL terminal setup

[wangdong-sd]

Describe the feature or problem you'd like to solve

No response

Proposed solution

I can not get the point why this does not support WSL terminal setup provided a MS product.
Please support it. And vim style will be better.

Example prompts or workflows

No response

Additional context

No response

[dogmatic69]

Works for me on WSL just fine. Perhaps be more specific with your errors.

[wangdong-sd]

I mean the command to setup-terminal and the error I got when to run it:

   If you're running WSL from VS Code, Windsurf or Cursor, please switch to a supported terminal within the IDE (e.g. PowerShell or Command Prompt) and run
   `/terminal-setup` again.`

I ran it from WSL and the shell is fishell.
did I miss anything?

[matt-FFFFFF]

I would like to see this more broadly supported in many terminals. Why not have an override that allows the caller to control this, rather than an artificial limit.

[dnoriegagoodwin]

For me, this is one of the biggest pain points.

It makes it feel like this CLI product is not actually a "terminal-first" product -- that it's really something that is designed to be run in and IDE.

What you get running /terminal-setup in Windows Terminal with Powershell Core 7

 ✘ No supported terminal detected. `/terminal-setup` is supported only in VS Code, Cursor and Windsurf.

And in WSL (as noted above)

 ✗ WSL terminal detected.

   If you're running WSL from VS Code, Windsurf or Cursor, please switch to a supported terminal
   within the IDE (e.g. PowerShell or Command Prompt) and run `/terminal-setup` again.

Both these comments give me the impression that Copilot CLI is not being designed by people who love terminal. Versus Claude Code feels like it is.

[brettcannon]

The lack of support is Windows Terminal itself. Trying to run /terminal-setup under PowerShell on Windows in Windows Terminal:

[brettcannon]

FYI https://github.blog/changelog/2025-10-17-copilot-cli-multiline-input-new-mcp-enhancements-and-haiku-4-5/#multiline-input says multiline support requires kitty keyboard protocol support. microsoft/terminal#11509 is the issue for adding such support to Windows Terminal.

[strayge]

Can confirm that multiline input (shift+enter) works in WSL with Windows Terminal Canary (1.26.611.0).
install link in Windows Terminal readme file

[examon]

This has been addressed across two releases. In v1.0.3, Windows Terminal was added as a supported /terminal-setup target for native Windows use. In v1.0.10, the misleading error shown when running /terminal-setup from WSL was removed. Also, WSL users on newer Windows Terminal builds with Kitty keyboard protocol support already get multiline input without any setup step. If you're still seeing this in a current release, please reopen with your CLI version and terminal details.