8 people reported

All time, since Sep 24, including 6 thumbs-up on GitHub.

Ctrl+Enter doesn't send queued messages

“In iTerm2, pressing Ctrl+Enter doesn't send the message.”

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/issues/1569/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

Ctrl+Enter fails to send queued messages immediately. After the 'ctrl+enter to send now' hint, iTerm2 opens its context menu; Windows Terminal conflicts with new line in prompt.

Is this your bug?

File my report
Where
Message queue
Versions
2.1.281 to 2.1.282
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Part of: Prompt newline/send key bindings misbehave3 bugs

  1. Shift+Enter and Ctrl+Enter submit instead of newline on VTE/xterm3 people
  2. Ctrl+J newline can't be unbound2 people

Original reports2, newest first

  1. Ctrl+Enter to send a queued message opens iTerm2's context menu instead#97163
  2. ctrl+enter not sending now#96796

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.