Type: Bug

VSCode Insiders Integrated Terminal with Fish Shell on Linux - Interactive Mode Key Handling Issue

VS Code version: Code - Insiders 1.110.0-insider (f5927e7, 2026-02-28T02:04:19.045Z)
OS version: Linux x64 6.17.7-ba25.fc43.x86_64
Modes:

System Info

Item	Value
CPUs	AMD RYZEN AI MAX+ 395 w/ Radeon 8060S (32 x 3513)
GPU Status	2d_canvas: enabled GPU0: VENDOR= 0x1002 [Google Inc. (AMD)], DEVICE=0x1586 [ANGLE (AMD, Radeon 8060S Graphics (radeonsi strix_halo ACO), OpenGL ES 3.2 Mesa 26.0.0)], DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.0 ACTIVE Machine model name: Machine model version: direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off webnn: disabled_off
Load (avg)	1, 1, 1
Memory (System)	125.08GB (102.44GB free)
Process Argv	/home/bogdan/mp-editor
Screen Reader	no
VM	0%
DESKTOP_SESSION	plasma
XDG_CURRENT_DESKTOP	KDE
XDG_SESSION_DESKTOP	KDE
XDG_SESSION_TYPE	wayland

Extensions disabled

Description

When using the VSCode Insiders integrated terminal with the Fish shell on Linux, commands that enter interactive mode (such as selecting options with arrow keys, or opening a TUI application) experience severe key handling issues.

Steps to Reproduce

1. Open VSCode Insiders on Linux (tested on Bazzite 43/Kinoite)
2. Set the integrated terminal shell to Fish (fish)
3. Run any of these specific interactive commands:
   • bun update -i
   • gh run workflow (and related gh interactive commands)
   • gh run watch
   • Any interactive GitHub CLI (gh) command
4. Attempt to interact with the interactive interface using keys like:
   • Enter
   • Space
   • Ctrl+C
   • Ctrl+X
   • Arrow keys (sometimes work partially, but not reliably)
   • Any other meta or control keys

Important Observation

Commands like htop or btop (non-Node/Bun applications) work perfectly well with all key bindings functioning as expected. The issue appears to be specific to Node.js or Bun-based interactive applications.

Expected Behavior

Keys should function normally in interactive mode, allowing navigation, selection, and control of the interactive interface.

Actual Behavior

When in interactive mode:

• Pressing Enter has no effect
• Pressing Space does nothing
• Control keys like Ctrl+C and Ctrl+X don't work
• Arrow keys may work partially but are unreliable
• The interactive interface becomes unresponsive to most key inputs

Environment

• VSCode Version: 1.110.0-insider
• Commit: f5927e7
• Date: 2026-02-28T02:04:19.045Z
• Electron: 39.6.0
• ElectronBuildId: 13330601
• Chromium: 142.0.7444.265
• Node.js: 22.22.0
• V8: 14.2.231.22-electron.0
• OS Version: Bazzite 43 (Kinoite, Linux x64 6.17.7-ba25.fc43.x86_64)
• Shell: Fish 4.2.0
• Extensions Disabled: Yes (restarted with --disable-extensions)

Fish Shell Configuration Details

• Version: Fish 4.2.0
• Custom Functions: None (directory ~/.config/fish/functions/ is empty)
• Custom Completions: None (directory ~/.config/fish/completions/ is empty)
• Key Bindings: Using default fish_default_key_bindings
• Terminfo: TERM variable not explicitly set in the current context
• Environment: Running on Wayland (KDE Plasma 6)
• Default Configuration: No significant customizations to Fish shell configuration

Additional Notes

• The issue does NOT occur in the stable version of VSCode (1.109.5)
• The issue persists after restarting VSCode Insiders
• The issue occurs even with all extensions disabled
• The interactive commands work perfectly well in:
  • The system's native terminal (Konsole)
  • The VSCode Stable integrated terminal
  • The Fish shell running outside VSCode

Impact

If this issue lands in the next stable release of VSCode, users who use interactive commands with the Fish shell will be forced to either:

1. Downgrade to the previous stable version
2. Switch to a different shell (losing Fish-specific workflow benefits)
3. Use an external terminal application

---

I have attached videos demonstrating the issue:

https://github.com/user-attachments/assets/25497128-932b-449f-8967-4294f1afe7a6
https://github.com/user-attachments/assets/a66bfdfb-ba3c-4472-b38a-709e928b5936