-
Notifications
You must be signed in to change notification settings - Fork 38.9k
Integrated terminal: Ctrl+C no longer interrupts running processes (regression in Insiders) #295372
Copy link
Copy link
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
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