Ctrl+Enter (queue message) is stolen by the "install plugin/extension" suggestion dialog

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Where does the bug appear (feature/product)?

Cursor IDE — Chat / Agent input

Describe the Bug

Ctrl+Enter is my keybinding to queue a message in chat. When Cursor is
showing one of its transient suggestion dialogs above the input — specifically
the “install this plugin/extension” suggestion — pressing Ctrl+Enter triggers
that suggestion (opens the plugin install dialog) instead of queueing my
message.

This looks like the same class of keybinding-priority bug already reported and
tracked for other dialogs, just with a new trigger:

The plugin suggestion itself is fine. The problem is that a common, expected
input keybinding (Ctrl+Enter) should never be intercepted by a passive
suggestion dialog I haven’t interacted with.

Steps to Reproduce

Steps to Reproduce
Be in a chat where Cursor is surfacing a plugin/extension install suggestion
above the input.
Type a message.
Press Ctrl+Enter to queue it.
Instead of queueing, the plugin install suggestion is triggered

Expected Behavior

Expected Behavior
Ctrl+Enter should always queue/send the message in chat. Transient suggestion
dialogs should only react to Enter/Ctrl+Enter when they actually have focus,
or via a dialog-specific hotkey — not by globally capturing the input
keybinding. Dialogs should not be given priority over the message input.

Operating System

Windows 10/11

Version Information

Version: 3.6.31
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Arch: x64
OS: Windows 11 (10.0.22631)

For AI issues: which model did you use?

Applies to Opus, GPT, Composer

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

This is a known class of bug - transient suggestion dialogs (like the plugin install suggestion, “Try Plan Mode”, etc.) intercepting the submit keybinding before the chat input gets it. The plan mode variant was fixed earlier this year, but the plugin suggestion variant you’re hitting hasn’t been fully resolved yet.

Our team is aware of this specific variant.

One thing that would help narrow this down: do you have the built-in “Submit with Ctrl+Enter” setting toggled on? You can check in Cursor Settings > Chat > Submit with Cmd+Enter. The fix for this class of bug relies on that specific setting to remap the plugin suggestion shortcut to Ctrl+Alt+Enter. If you’re using a custom keybinding for Ctrl+Enter instead, the remap won’t activate, which could explain why the conflict persists.

You may also find this related thread helpful, where another user reported the same plugin suggestion conflict on macOS: Cursor detect plugins from chat and installation collides with Command+Enter

In the meantime, as a quick workaround, you can dismiss the plugin suggestion by pressing Escape before sending your message.