Repository navigation
First input gets ignored on pwsh/conpty #243584
Description
- Open Insiders on Windows
- Open the terminal, immediately type in
git status, and press enter it statusappears to be typed into the terminal, and the terminal gives an error.
I'm not sure if it's from the history, shell integration, or suggest feature.
Reacted by Alex Ross, Gabriele Tomberli, Nicolas HENRY, Frulfump, Harry Robbins, M393, heartacker and andrejs82git
Activity
meganrogge commentedon Mar 14, 2025
Raymond Zhao (@rzhao271) can you repro with suggest disabled? also, looks like shell integration isn't working for you after restart?
Tyriar commentedon Mar 17, 2025
This is mainly #241978, the
gcould have accidentally not been typed or been swallowed by pwsh on startup./duplicate
Tyriar commentedon Mar 24, 2025
This first input is happening, I think it might be related to the recent conpty version bump.
35 remaining items
u84six commentedon Oct 16, 2025
I've been dealing with this issue for a couple years now. I can confirm that it only happens when using git bash as the default terminal, and only happens in vscode integrated terminal. I haven't been able to reproduce this in Windows Terminal (in which I also use git bash). The interesting thing is that it's more prominent now because of Copilot and other agentic AI that relies on terminal use, so it breaks a lot more than just having to backspace and retype. I'm thinking it's a race condition between vscode terminal event and the time git bash responds... something like that. Considering that it doesn't happen in other terminals, I hope the vscode team can resolve this at some point because it breaks Copilot here and there and causes me to have to redo commands (which eats tokens).
A good example is when I setup vscode to initialize my Python venv environment:
{ "python.defaultInterpreterPath": "${workspaceFolder}/.venv", "python.terminal.activateEnvironment": true, "python.terminal.activateEnvInCurrentTerminal": true }Sometimes I get the error:
ource c:/Users/[username]/Development/projects/[projectname]/.venv/Scripts/activate bash: ource: command not foundTyriar commentedon Oct 18, 2025
u84six I'm assuming you're being hyperbolic or something as this issue definitely only started happening within the past year. February at the earliest I believe if you had an experimental setting on microsoft/node-pty#759
Tyriar commentedon Oct 18, 2025
We got to the bottom of it and it should be fixed in the upcoming release: #271556
u84six commentedon Oct 19, 2025
Well you should know better than me 😉
anthonykim1 commentedon Oct 22, 2025
Everyone, please try out the latest vscode-insiders (Yes this is different from your regular blue icon VS Code), insiders will be green icon: https://code.visualstudio.com/insiders/
And please give us a confirmation, this particular issue should be resolved!
Thanks
u84six commentedon Nov 17, 2025
Is 1.106.0 the release that supposedly has this fix? Because I can confirm that it's still an issue.
Tyriar commentedon Nov 19, 2025
u84six are you on git bash? You might be seeing #275625 as I believe this is fixed for pwsh specifically.
u84six commentedon Nov 19, 2025
Yes, it's a bit confusing considering it's the same kind of bug. Will the git bash defect eventually get addressed?