GitHub Copilot on Terminal Chat wrongly treat path as shell #22653

Closed
opened 2026-01-31 08:19:34 +00:00 by claunia · 2 comments
Owner

Originally created by @doggy8088 on GitHub (Dec 12, 2024).

Windows Terminal version

1.23.3461.0

Windows build number

10.0.19045.5131

Other Software

N/A

Steps to reproduce

  1. Add a new profile in the Windows Terminal Canary. The command line is C:\Program Files\PowerShell\7\pwsh.exe -NoLogo.

  2. Open a new tab to this profile

  3. Open Terminal Chat

  4. Enter list files

  5. You will see "Program" shell which is wrong.

    Image

    GitHub Copilot seems treat C:\Program Files\PowerShell\7\pwsh.exe -NoLogo as a Program shell. This should be a bug.

Expected Behavior

The shell of the C:\Program Files\PowerShell\7\pwsh.exe -NoLogo should be pwsh.

Actual Behavior

The shell of the C:\Program Files\PowerShell\7\pwsh.exe -NoLogo become Program shell.

Originally created by @doggy8088 on GitHub (Dec 12, 2024). ### Windows Terminal version 1.23.3461.0 ### Windows build number 10.0.19045.5131 ### Other Software N/A ### Steps to reproduce 1. Add a new profile in the Windows Terminal Canary. The command line is `C:\Program Files\PowerShell\7\pwsh.exe -NoLogo`. 2. Open a new tab to this profile 3. Open Terminal Chat 4. Enter `list files` 5. You will see "Program" shell which is wrong. ![Image](https://github.com/user-attachments/assets/57e151e7-2629-4481-a8ee-04f67a4193e5) GitHub Copilot seems treat `C:\Program Files\PowerShell\7\pwsh.exe -NoLogo` as a `Program` shell. This should be a bug. ### Expected Behavior The shell of the `C:\Program Files\PowerShell\7\pwsh.exe -NoLogo` should be `pwsh`. ### Actual Behavior The shell of the `C:\Program Files\PowerShell\7\pwsh.exe -NoLogo` become `Program` shell.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:19:35 +00:00
Author
Owner

@DHowett commented on GitHub (Dec 12, 2024):

Thanks!

In general, and for safety reasons, you should use quotes when you include a path with spaces in it.

We should handle this better, but you can get around the bug today by quoting the EXE path 🙂

@DHowett commented on GitHub (Dec 12, 2024): Thanks! In general, and for safety reasons, you should use quotes when you include a path with spaces in it. We should handle this better, but you can get around the bug today by quoting the EXE path 🙂
Author
Owner

@doggy8088 commented on GitHub (Dec 12, 2024):

After adding quote on it, it works perfectly. Thank you! :)

@doggy8088 commented on GitHub (Dec 12, 2024): After adding quote on it, it works perfectly. Thank you! :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22653