Shift+Enter blocked in Cursor "editor area" terminals but not VS Code

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I use CLI coding agents (Claude Code, Codex, Factory) inside Cursor, and Shift+Enter does not add a newline as expected when run in a terminal in the “editor area”.

It’s definitely a Cursor issue, as I tested VS Code and they all work fine. I can repo across all 3 of these coding agents, or just in a terminal with no CLI tool. Cursor is the cause here, not eg Claude Code.

It only affects terminals in the “editor area”, terminals in the “terminal area” work fine.

It was previously reported here but seems to have regressed: Shift+Enter not working in the latest version of Cursor IDE(Claude Code Extension) - #17 by matteoFeduzi

Providing more repro details here, in hopes it can be fixed. If not, I’ll likely switch to VS Code as this issue makes coding agents quite unusable in Cursor.

Steps to Reproduce

  1. Create a new terminal in the “editor area”
  • Command Palette > “Terminal: Create New Terminal in Editor Area”
    (aside: this is how terminals are created by the Claude Code or Factory Droid VS Code extensions)

  1. Type “claude” or “droid” to open a coding agent (installed previously)

  2. Type shift+enter

This should add a newline, but instead it submits the chat message.

Note:

  • If you instead use “Terminal: Create New Terminal”, it works as intended. I’m guessing Cursor (but not VS Code) is doing something to intercept editor area terminal events that’s causing this.

Expected Behavior

Shift+Enter should not be blocked.

I have keybindings setup but Cursor is blocking the “Enter” key before it gets to the KeybindingService.

To confirm this, run:
Command Palette > “Developer: Toggle Keyboard Shortcuts Troubleshooting”

Open a terminal in the “terminal area” at the bottom and type “shift+enter”. I see this in the debug output (as intended):
[KeybindingService]: | Resolving shift+[Enter]

But if I open a terminal in the “editor area”, I instead see this:
[info] [Window] [KeybindingService]: / Received keydown event - modifiers: [shift], code: ShiftLeft, keyCode: 16, key: Shift
[info] [Window] [KeybindingService]: | Converted keydown event - modifiers: [shift], code: ShiftLeft, keyCode: 4 (‘Shift’)
[info] [Window] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[info] [Window] [KeybindingService]: + Ignoring single modifier shift due to it being pressed together with other keys.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 23.6.0

Additional Information

Users are also reporting this here: [BUG] /terminal-setup command doesn't work in VSCode · Issue #1251 · anthropics/claude-code · GitHub

But after debugging last few hours, I’m convinced it’s a Cursor issue, not a Claude Code issue.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
2

Hi Matt,

Thank you for reporting this. This issue is on our radar, and we’ve been able to reproduce it. It appears that any keyboard shortcut just gets ignored when using the terminal in the editor window.

We’re working to prioritize it alongside other ongoing work. Rest assured, you’re not alone in reporting this concern. We appreciate your patience. :pray:

2 Likes
3

Great - thanks for your response!

If it helps at all, I was surprised to find today that latest VS Code (on macOS at least) doesn’t have this issue. I tried to track down where the difference was coming from (disabled all extensions, same settings, etc) but couldn’t find anything in user space to explain it. Still, maybe a clue for you…

Thanks for listening!

1 Like
4

Same experience here.

5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.