[BUG]: `Shift+Return` keybind shortcut isn't working to open a new line

[koushikxd]

Description

Issue: Shift + Return (and other newline shortcuts) not working in OpenCode on macOS

Environment

• macOS
• Ghostty + tmux
• Recently switched from Cursor to OpenCode

Description

I usually press Shift + Return to insert a new line in chat inputs. In OpenCode, this does not work.

The keybind documentation shows:

"input_newline": "shift+return,ctrl+return,alt+return,ctrl+j"

However, none of these shortcuts work except for Ctrl + J.

When I press Shift + Return, Ctrl + Return, or Alt + Return, the message is sent immediately instead of inserting a new line.

Shift + Return works as expected in Claude Code and Cursor for me. This issue only occurs in OpenCode.

Plugins

none

OpenCode version

1.2.17

Steps to reproduce

1. Type something in the input
2. press any one of the newline keybinds ("shift+return,ctrl+return,alt+return,ctrl+j")
3. none of the keybinds will work except for ctrl+j and the message will be directly sent to the chat

Screenshot and/or share link

Screen.Recording.2026-03-05.at.1.24.01.AM.mov

Operating System

Latest MacOS

Terminal

Ghostty

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Shift-return does not input newline since 1.0 #4046: Shift-return does not input newline since 1.0
• windows: cannot type in newline with shift enter. #8038: windows: cannot type in newline with shift enter
• shift+Enter is submitting the response after pasting something insted of NewLine #10877: shift+Enter is submitting the response after pasting something instead of NewLine
• Keyboard keybinds configuration not working - input_newline: shift+enter ignored #11983: Keyboard keybinds configuration not working - input_newline: shift+enter ignored
• unable to insert new line in prompt box in MacOS Tahoe basic Terminal #7248: unable to insert new line in prompt box in MacOS Tahoe basic Terminal

For keybind-related issues, please also check our pinned keybinds documentation: #4997

[MilesNorton]

@koushikxd I'm getting this. I think it is related to tmux, are you able to confirm it works in Ghostty without tmux for you?
I removed Tmux and it worked for me

My Environment

• Linux (ubuntu)
• Alacritty
• Tmux

[koushikxd]

@MilesNorton i just did a bit of research and i found out that tmux was the culprit.

The actual fix:

• add this line below inside your tmux.conf and the issue should be resolved

set -g extended-keys always

[MilesNorton]

cheers @koushikxd. I set that as well as changing always to on and that still hasn't worked for me.