Ctrl+Enter to send a queued message opens iTerm2's context menu instead
Status Open
Reported on v2.1.282
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 3 comments · opened Sep 25, 2026
Messages I send while Claude is responding get queued, and Claude Code shows the hint ctrl+enter to send now. In iTerm2, pressing Ctrl+Enter doesn't send the message. It opens iTerm2's right-click menu, and the message stays queued.
Steps to reproduce
- Run
claudein iTerm2 with default settings. - Send a message while Claude is responding, so it gets queued.
- Press Ctrl+Enter.
Expected: The queued message sends.
Actual: iTerm2's context menu opens and nothing sends.
Possible cause: With default settings, iTerm2 may not pass Ctrl+Enter through as a distinct key. If so, the hint should suggest a shortcut that works in the current terminal, or /terminal-setup should configure it.
Environment
- Claude Code 2.1.282
- iTerm2 3.4.4,
TERM=xterm-256color, no tmux - macOS 26.6.2
- No custom keybindings
3 Comments
On Ghostty it toggles full screen mode.
On Windows Terminal it adds a new line: https://github.com/anthropics/claude-code/issues/96796
Possible workaround:
Ctrl+Enterbut theEnterkey from the numpad, that exists on full-size keyboards. With Ghostty it does not toggle the full screen mode, and reach Claude Code.Same problem in Terminal.app and VS Code on macOS. In the former, Ctrl-Enter opens a context menu in the GUI. In the latter, it does absolutely nothing. Confirmed by using
cat.