[FEATURE] Suggestion: Don't auto-submit on Enter
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 15 comments · opened Dec 19, 2025 · closed Jun 1, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
This is related to [https://github.com/anthropics/claude-code/issues/729](url)
Claude doesn't let you set the Enter/ Shift+Enter behavior.
Many people want to press Enter to send a newline, not to send a message. It breaks the flow in long messages.
Proposed Solution
That thread was closed but many people found it annoying.
If anyone is interested there is a workaround here:
https://github.com/kuitog/Claude-Chatgpt-Use-Enter-as-a-Newline
Alternative Solutions
_No response_
Priority
Low - Nice to have
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
14 Comments
---
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
---
You can use alt+Enter and it works fine
@benmassaoud The whole point is NOT to have to use shift+enter, just like in normal text editing: you press enter and you insert a newline.
I think opening the editor for long messages is better, but you do lose the filename expansion feature then. Pressing ctrl-enter to submit this comment ;-)
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This has been shut down multiple times by anthropic. Honestly, there are many AI platforms out there, with common sense for the end user. Just going to switch to one of them. Most of these spin offs like Claude, will eventually collapse. This type of behavior will just accelerate that. Good luck
I've walked through about 5 similar issues about this very basic feature, and all of them are closed by Anthropic. Gotta burn those user tokens somehow, right?
Enter == New Line
CMD + Enter == Send Prompt
This is the way most apps are leaning and it's most intuitive.
or just allow custom keybinds please
Following up on this - the below worked perfectly for me until a few days ago where the whole UI got revamped.
I'm still able to insert a newline with a simple press on the Enter key, but CTRL+ENTER became inactive and is not sending the prompt anymore.
<img width="720" height="85" alt="Image" src="https://github.com/user-attachments/assets/642ecf19-d75d-4cc8-a946-ade941f3983f" />
@AviBueno
Note that your proposed solution is VS Code _specific_, while the main request was for Claude Code CLI _in general_.
@informatik01 thanks for pointing that out!
I was filtering the issues by VSCode and somehow got this one.
EDIT: Created a standalone bug report
Honestly: It is driving me mad. It is impossible to write a sensible prompt if every new line you are at risk to fire off your message, which then triggers 20 pages of irrelevant output. It's not only annoying - this costs Anthropic real money and huts the environment, because you are generating endless tokens without actually having specified the problem. Why is the firm so completely oblivious to the issue?
It would be great if the web interface could be configured so that when pressing Enter while typing a message, the cursor simply moves to a new line. The message could then be sent by pressing Ctrl+Enter. It’s very annoying to have to constantly remember to press Shift+Enter to move to the next line. Many messengers have this feature, and it’s very convenient when messages are long and structured.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.