getcursor
CTRL + BACKSPACE shortcut, what were you thinking...
Hi team,
I wanted to raise an issue regarding the keyboard shortcut CTRL + BACKSPACE, which currently rejects the last agent edit in Cursor.
On Windows (and many Linux environments), CTRL + BACKSPACE is a universally accepted shortcut to delete the previous word, a deeply embedded muscle-memory action for developers and writers alike. In Cursor, using it instead rejects the last edit, which can lead to unintentionally discarding useful AI output simply because of a reflexive key press.
There is an option in settings to remap this behaviour, and I did change it months ago, but every time the app updates, it reverts back. This makes the problem even more frustrating, as I keep assuming it’s fixed, only to accidentally reject work again.
It seems wild that a team of developers would choose to override such a standard shortcut with something so destructive, especially one so tightly wired into developer muscle memory. Surely this should never be the default?
Suggestions:
Change the default binding for "Reject Last Edit" to something less collision-prone (e.g. CTRL + ALT + Z, or something customisable).
Persist shortcut settings across updates reliably.
Consider aligning more closely with OS-level expectations for standard keyboard shortcuts.
Thanks, I really enjoy using Cursor otherwise, but this one issue keeps catching me out and breaking flow.
I’m honestly at my wit’s end with Cursor right now. I've spent well over a thousand dollars on this tool over the past five months, and somehow, the experience is getting worse. I don't say this lightly, but the decisions being made around basic usability are absolutely baffling. It's as if you're deliberately ignoring decades of established interface behaviour.
Let’s talk about your core interface, the prompt input. This should be rock solid. It’s where we, as users, spend 90% of our time. And yet:
Arrow Key Navigation – Seriously, why does pressing UP repeatedly inside the text area suddenly jump me out of it? No app I’ve ever used behaves this way. No terminal. No IDE. No code editor. This is not a quirky opinion — it's a universal expectation for how inputs work. This behaviour is infuriating and breaks flow every single time it happens.
Code Blocks That Can’t Be Copied; What? You’ve styled your terminal/command output blocks in a way that looks selectable — but try pressing CTRL + C, and nothing happens. Why are we unable to copy simple code snippets with the most basic keyboard shortcut? This is the sort of friction that drives users mad, especially in a developer tool where copying commands is a constant action. Again — this is expected default behaviour in every other tool.
I also previously reported the CTRL + BACKSPACE issue — a fundamental shortcut on Windows and Linux that you’ve hijacked to reject agent output. You do offer a way to change this in settings, but it resets with every update. This is an outrageous default to begin with, and the fact that settings don’t persist makes it actively hostile to use.
Let me be clear: you're not just breaking expected behaviour, you're replacing it with actions that destroy work. That’s not innovation, that’s user sabotage.
Actionable suggestions (again): Do not override globally standard keyboard shortcuts with destructive actions.
Fix your input field to behave like a proper multi-line editor.
Ensure all output blocks (especially code/terminal examples) can be copied with standard keyboard shortcuts.
Persist user settings across updates. This should be table stakes.
I really want to keep using Cursor. But right now, it feels like the core design choices are being made without any empathy for the people using it day-in, day-out. Please sort this out.
