Shift+Enter not inserting newline in native version (iTerm2/macOS)

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/18464
2. https://github.com/anthropics/claude-code/issues/19386
3. https://github.com/anthropics/claude-code/issues/18886

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

I've run into this as well. For now, I've found Option + Enter will reliably submit a new line... what a strange regression.

Same here on Linux in PyCharm. Just switched to the native version two days ago but only noticed this now. Alternatives are Ctrl + Alt and Ctrl + J. Shift + Enter should work, too, though, as that's pretty common.

I'm getting this in the current desktop buid. For me neither shift nor option work in the code tab (but do work in Chat).

This just started occurring today and is extremely annoying.

I asked Claude Chat if this was new behavior and why it was implemented, noting that ONLY Claude Code behaves this way and that Claude Chat and Claude Cowork process Shift+Enter as normal.

Claude's response was basically this:

Shift+Enter was never deliberately supported in any part of Claude for Mac, and if Chat and Cowork supported it, that was a mistake. You're right that Shift+Enter is how the entire rest of the macOS ecosystem works, but Claude for Mac cannot be reconfigured this way, so you're stuck with Backslash Enter as the only way to insert a newline.

This is a small annoyance that will rapidly become a HUGE annoyance as it that will interfere with my workflow x500/day. This needs to be prioritized and fixed posthaste.

please make this somehow configurable similar to how openAI Codex does!
As for the newest native App on Mac neither SHIFT+ENTER or CMD+ENTER seems to do the trick with newlines which makes entering longer text without any human readable formatting a real pain!

<img width="665" height="68" alt="Image" src="https://github.com/user-attachments/assets/7046c045-164a-48e0-b88a-454bdecc6f91" />

This just started occurring today and is extremely annoying. I asked Claude Chat if this was new behavior and why it was implemented, noting that ONLY Claude Code behaves this way and that Claude Chat and Claude Cowork process Shift+Enter as normal. Claude's response was basically this: > Shift+Enter was never deliberately supported in any part of Claude for Mac, and if Chat and Cowork supported it, that was a mistake. You're right that Shift+Enter is how the entire rest of the macOS ecosystem works, but Claude for Mac cannot be reconfigured this way, so you're stuck with Backslash Enter as the only way to insert a newline. This is a small annoyance that will rapidly become a HUGE annoyance as it that will interfere with my workflow x500/day. This needs to be prioritized and fixed posthaste.

Yes. Just started today which is odd given I haven't made any environment changes. Have you found a workaround?

Option Enter isn't working, neither is \ + Enter

Started today:
Claude code - web interface in browser always respected Shift+Enter for carriage return, as of today, holding Shift when pressing Enter does nothing. The prompt is immediately sent.
Tried workaround - creating multi-line multi-paragraph prompt in a separate editor in a markdown format, with proper formatting. Then copied and pasted into the input field and pressed Enter. All carriage returns and new line breaks have been stripped out, prompt was sent for execution with a single-space separation.

Same here with Code panel in Claude Desktop. In Chat panel Shift+Enter _does_ create a new line.

Yes, not working on Windows 11 either.

thanks for the report! the fix is landed

thanks for the report! the fix is landed

What does this mean? I noticed that there is a new build of Claude for Mac available. But I updated in the Claude app, tried again, and didn't have fixed Shift+Enter behavior in Claude Code. Then I downloaded the latest Claude for Mac build directly from Anthropic, installed and ran it, and tried again - still not fixed.

How long does the fix take to make it into prod builds?

@neuron-whisperer the fix be released now, can you try again?

@antonpk1 Yep, it's good now. Glad to have this functionality back. Thank you!

Which version has the fix?

Which version has the fix?

I'm running 1.1.2685 (f39a62) and it behaves as it should.

For me - I needed to to add a new mapping in iterm2

In iTerm2 Settings > Profiles > Keys, create a new mapping for Shift+Enter with action "Send Hex Code" and value 0x1b 0x0d

Still seeing this regression on Claude Code v2.1.63 (macOS). Shift+Enter submits the message instead of inserting a newline, despite having "shift+enter": "chat:newline" in keybindings.json. Option+Enter works as a workaround.

Still seeing this regression on Claude Code v2.1.63 (macOS). Shift+Enter submits the message instead of inserting a newline, despite having "shift+enter": "chat:newline" in keybindings.json. Option+Enter works as a workaround.

A fix to this if you are on mac is go to:
/Users/(your user)/Library/Application Support/Code/User/keybindings.json

delete that file and then run /terminal-setup again in claude code

It remakes the file and shift-return works again

This fix does not work on kitty since "kitty is natively supported". Broken on kitty since v71 though