Prioritize ESC key: Dismiss IDE Autocomplete before Cursor Prediction

Ideas Feature Requests
,
1

Hi Cursor Team,

Currently, when both the IDE autocomplete modal and a Cursor Tab prediction are visible, pressing Esc dismisses both at once.

I want to configure a staged dismissal so that:

1.	1st Esc press: Only closes the IDE autocomplete menu.
2.	2nd Esc press: Dismisses the Cursor ghost text prediction.

This would allow me to clear the menu “noise” to better see the Cursor prediction without losing both.

Could you provide the correct context keys and command IDs to achieve this? I am looking for something like:


{
  "key": "escape",
  "command": "hideSuggestWidget",
  "when": "suggestWidgetVisible"
},
{
  "key": "escape",
  "command": "cursor.cpp.dismiss", // Need correct ID
  "when": "cursorPredictionVisible && !suggestWidgetVisible"
}

What are the specific when clauses used by Cursor’s Tab-completion engine to make this work?

Thanks!

3

Hey @teziovsky!

Thanks for the feedback. Unfortunately, Curosr uses a global DOM event listener for the escape key that completely overrides any keybindings. I’ve moved your post under Ideas.

1 Like