Regression: Keyboard Shortcuts Broken With Integrated Terminal

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Detailed description is provided in the Discussion channel:

Steps to Reproduce

Set “terminal.integrated.defaultLocation”: “editor” and open a new terminal. Once opened in editor area, try any workbench command like Ctrl + P or Ctrl + Tab or Ctrl + K. All these commands are sent to terminal instead of to the workbench.

Expected Behavior

Keyboard shortcuts that are meant for the workbench must not be sent to terminal.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54 (user setup)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known issue the team is already working on.

This bug was introduced in v1.6 and affects all modifier-key shortcuts when the terminal is opened in the editor area via “Create New Terminal in Editor Area.” Your issue with Ctrl+P, Ctrl+Tab, and Ctrl+K has the same root cause as the related threads.

Workaround: instead of using “Create New Terminal in Editor Area,” open a regular terminal and drag it into the editor area. Keyboard shortcuts should then work without requiring a reload.

The team is working on a fix. I’ll link your report to the ongoing investigation.

1 Like

Great to know team is working on this. Awesome! And thanks so much.