-
Notifications
You must be signed in to change notification settings - Fork 37.3k
Open
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugterminal-shell-fishAn issue in the terminal specific to fish, including shell integrationAn issue in the terminal specific to fish, including shell integrationterminal-shell-integrationShell integration infrastructure, command decorations, etc.Shell integration infrastructure, command decorations, etc.
Milestone
Description
Testing #286022
This one is interesting
Set "chat.tools.terminal.preventShellHistory": false then use fish shell.
How to repro (see the video too):
- Run some command to run in terminal via copilot
- Look at run recent command. It is fine
- Run second command to run in terminal via copilot
- 🐛 Run recent command polluted with
welcome to fish...etc
copilotRunRecentSad.mov
The interesting thing is that when commands are ran manually run recent command is NOT polluted:
Screen.Recording.2026-01-06.at.9.03.47.AM.mov
Im not sure what the difference is between running command manually vs. via copilot, but surprised run recent command behaves differently.
Another interesting find:
Without starship run recent command are not polluted even when commands are ran via copilot:
Screen.Recording.2026-01-06.at.9.10.57.AM.mov
Maybe this is my issue🧐 starship somehow messing up? I noticed A and D are little off-position:

Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugterminal-shell-fishAn issue in the terminal specific to fish, including shell integrationAn issue in the terminal specific to fish, including shell integrationterminal-shell-integrationShell integration infrastructure, command decorations, etc.Shell integration infrastructure, command decorations, etc.