I would like to ask you to add, in the Cursor settings, the possibility of disabling the sending of the chat through the Enter key and leaving only the sending with the button so that the chat is not sent by mistake thinking of going to a new line, as has happened to me several times. I imagine that this is a feature desired by many users.
Thank you.
17 Likes
actually, try Shift+ Enter
1 Like
Hi thepKz, I know that if I press Shift + Enter I get a line break in the text but since in practically all other editors on the market you go to a line break by pressing only the Enter key, it is automatic to press Enter and in this way you send the chat when perhaps you have not yet finished the request. If the developers put in the Cursor settings the possibility of sending only with the send button they will also save the resources of Cursor which sees many requests arriving that will then be immediately blocked. For users who are happy with how the editor behaves now, just do not set the flag.
2 Likes
Dude, no.
Hi leoing, why no?
1 Like
It’s the worst UI ever 
I do not think like you. It is a feature that facilitates the habits of developers to create a new line of text with the Enter key and reduces traffic to the servers of Cursor for chat sent still not finished. For me it is absolutely a feature to implement.
1 Like
Hi leoing, I think it would be good at least to have the option to disable it.
It’s always better to have the option than not.
6 Likes
Is this available yet? I accidentally submit all the time. I’m resorting to writing things in a markdown file, copy and paste to prevent this This feels even more important when working with the new “Plan” feature. I’m ok with having to opt into this behavior. Slack has this in their advanced setting where Enter starts a newline and cmd + Enter sends. So I still user keyboard shortcuts.
2 Likes
As far as I know, they haven’t implemented it yet. Let’s hope they do.
I also tried editing the keybindings.json, but I couldn’t disable sending chat with the Enter key.
2 Likes
I fully agree with this request. While writing a single prompt, you could need to add a line break N times, while the need of sending the prompt is only once. It really makes sense to allow the Enter behavior to be a new line, and use Shift + Enter to send it once it’s ready. Also, the consequences of accidentally sending a prompt are worse than the ones of accidentally adding a new line when trying to send.
2 Likes
Any word on this? Seems like a super simple feature to implement but would save headaches and tokens accidentally hitting enter on the keyboard when not finished typing the prompt and then having to quickly stop the operation to start again.
2 Likes
I don’t think it’s been implemented. Let’s hope they read the request and implement it!
Count me in as a user very annoyed by this. Most of my prompts are multi-line…
Hi olejorgenb,
I’m happy to announce to you and others that the Cursor team has decided to implement my request: Return key in chat - #2 by deanrie 
1 Like
Great! Thanks for the news, Lee.
Hi Lee, Cursor has been updated to version 2.4.30, but I don’t seem to see the option for the Enter key. Perhaps it will be released in another version?
My version of Cursor:
Version: 2.4.30 (user setup)
VSCode Version: 1.105.1
Commit: 0f8217a84adf66daf250228a3ebf0da631d3c9b0
Date: 2026-02-06T23:20:57.191Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Unfortunately, I don’t see it either. Perhaps it was moved to another location?
Version: 2.5.0
VSCode Version: 1.105.1
Commit: 71a9bb480f92182bcc374fe3b98630afd8252e60
Date: 2026-02-09T23:16:52.202Z
Build Type: Stable
Release Track: Nightly
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0
1 Like
I can confirm that it’s present in 2.5.12. Great! 
1 Like