Repository navigation
Closed
xtermjs/xterm.js
#5737Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-priorityIssue identified as high-priorityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-inputRelating to typing in the terminal not doing the right thing, IMEs not working, etc.Relating to typing in the terminal not doing the right thing, IMEs not working, etc.terminal-shell-fishAn issue in the terminal specific to fish, including shell integrationAn issue in the terminal specific to fish, including shell integrationupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.110.0-insider (0366405)
- OS Version: macOS 26.1 (Build 25B78)
Steps to Reproduce:
- Open the integrated terminal in VS Code Insiders.
- Use fish as the integrated terminal shell (fish at
/opt/homebrew/bin/fish). - Run
sleep 100(also seen withtop). - Press Ctrl+C.
Expected:
sleep is interrupted (SIGINT) and the shell prompt returns.
Actual:
The process keeps running, and the terminal prints something like [99;5u (sometimes repeated).
Additional Information:
- Only reproduces with fish (fish 4.4.0). If I switch the integrated terminal profile to zsh, Ctrl+C works normally.
- Outside VS Code, Ctrl+C interrupts as expected in fish (Ghostty and macOS Terminal).
$TERM:- VS Code:
xterm-256color - Ghostty:
xterm-ghostty - macOS Terminal:
xterm-256color(Ctrl+C works)
- VS Code:
- Ctrl+C also does nothing at the fish prompt (no running command).
- Disabling shell integration (
terminal.integrated.shellIntegration.enabled: false) does not change the behavior. - Reproducible with
fish --no-config. fish_key_readerprintsbind ctrl-c 'do something'in both VS Code and Ghostty.[99;5ulooks like a kitty keyboard protocol "CSI u" sequence for Ctrl+C.
Repro videos:
CleanShot.2026-02-14.at.14.07.27.mp4
CleanShot.2026-02-14.at.14.09.28.mp4
Reacted by Soner, Caleb Chan, Sworld, Daniel Mizsak, Tomáš Král, Andy Hall, Jérémi Robi, max-tremblay, Mike Lui, Malte Jürgens and 7 more
Metadata
Metadata
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-priorityIssue identified as high-priorityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-inputRelating to typing in the terminal not doing the right thing, IMEs not working, etc.Relating to typing in the terminal not doing the right thing, IMEs not working, etc.terminal-shell-fishAn issue in the terminal specific to fish, including shell integrationAn issue in the terminal specific to fish, including shell integrationupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeeded
Activity
howmanysmall commentedon Feb 14, 2026
Whoops, sorry, did this from CLI so it didn't seem to follow the template.
shyim commentedon Feb 15, 2026
This drives me crazy.
Maybe an easier reproducer:
you cannot control + c to escape 😭 .
meganrogge commentedon Feb 17, 2026
Cannot repro, thus closing. Try using
Developer: Toggle Keyboard Shortcuts Troubleshootingto debugbug-no-repro.mov
no-repro2.mov
shyim commentedon Feb 17, 2026
shyim commentedon Feb 17, 2026
Asked Claude:
And it's really fixed by disabling it 😆
this commit seems implemented that kitty keyboard protocol: fish-shell/fish-shell@8bf8b10
Edit: As those commands work in kitty + ghostty it must be a problem with vscode
cross linking: #294651
amyspark commentedon Feb 19, 2026
Can this be reopened? I can confirm this issue is reproducible through Remote SSH against Fish 4.5.0.
VS Code version:
Arctyc commentedon Mar 5, 2026
I can reproduce it on 1.110. How about we reopen?^[[99;5u^[[99;5u^[[99;5u^[[99;5u^[[99;5u^[[99;5u^[[99;5u^[[99;5u^[[99;5u
Additionally, it's worse if I switch to bash. Then backspace types u7 or something instead.
anthonykim1 commentedon Mar 5, 2026
This is very interesting. /cc Daniel Imms (@Tyriar)
I couldn't repro on 3.7.1, but was able to after updating Fish to latest:
After updating fish to latest:
^Cwas fine when testing in fish outside of VS Code. Will need to investigate18 remaining items
anthonykim1 commentedon Mar 10, 2026
Please try latest insiders. Insiders build
or more recent should have the fix
Verification steps:
[config.fish] Call `reset` in VS Code to fix `^C` and friends.
[config.fish] Remove the VS Code `reset` workaround.
tsangwpx commentedon Mar 15, 2026
Anthony Kim (@anthonykim1) thank for the fix. Now, the ENTER and BACKSPACE keys are working.
However, I am still experiencing the issue with Ctrl + C and other prefix + keys in fish shell in vscode, which used to work.
The
sleep 30is working but the shell itself cannot interact with prefix + key, e.g. Ctrl +C.The fish shells with issues are version 4.0.2 from debian trixie (stable) in WSL, and Ubuntu 25.10.
It is confirmed the fish 4.2.1 in debian forky (testing) is working.
Version: 1.112.0-insider (user setup)
Commit: 3d2f6d9
Date: 2026-03-14T08:46:55Z
Electron: 39.8.0
ElectronBuildId: 13470701
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045
radek-duchon commentedon Mar 17, 2026
For me it is even worse, I guess?! It is not only CTRL+C, but Backspace does stdout
^[[127u. When I open for examplenodethen enter does nothing, so I cannot execute.exit. I could go on...rtsui-mk commentedon Mar 18, 2026
Confirm this is fixed in latest 1.112 update.