13 people reported
All time, since Sep 21, including 7 thumbs-up on GitHub.
Prompt newline/send key bindings misbehave
“In a terminal, if I'm running claud, then shift-enter submits the command.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/themes/262/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
3 bugs in this theme
- Ctrl+Enter doesn't send queued messagesNo workaround yet8 people
- Shift+Enter and Ctrl+Enter submit instead of newline on VTE/xtermHas a workaround3 people
- Ctrl+J newline can't be unboundNo workaround yet2 people
What's included
- Shift+Enter or Ctrl+Enter submits the prompt instead of inserting a newline on xterm/VTE terminals, which arrive as a plain CR
- Ctrl+Enter shown as 'ctrl+enter to send now' for a queued message does not send it; iTerm2 opens its context menu, Windows Terminal sends inconsistently
- Ctrl+Enter send-now conflicts with newline in the prompt and cannot be rebound
- Setting "ctrl+j": null in keybindings.json still inserts a newline, in the CLI and the VS Code extension
- SKK Japanese IMEs insert stray newlines because Ctrl+J confirmation reaches the prompt as LF
Not included
- Other keybindings unrelated to newline or send not working
- Multi-line paste handling in the prompt
- IME composition problems not involving Enter or Ctrl+J
Original reports6, newest first
- VS Code extension: Ctrl+J newline is hardcoded in the chat input and can't be disabled#102749
- Shift-Enter submits command instead of creating newline in CLI#97355
- Ctrl+Enter to send a queued message opens iTerm2's context menu instead#97163
- ctrl+enter not sending now#96796
- modifyOtherKeys is only enabled for kitty-protocol/allowlisted terminals, so ctrl+enter can't be bound on xterm/VTE#96526
- Ctrl+J / LF newline is hardcoded in the chat input, so unbinding ctrl+j in keybindings.json has no effect (breaks SKK IMEs)#95957