You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature: Allow custom keybindings to send raw hex codes / OpenCode SHIFT+ENTER Fix. #8462
I would like the ability to map Shift+Enter (and other keys) to send specific hex codes / escape sequences (e.g., 0x1b 0x0d or \033OM) to the running terminal process, or for the issue to be resolved without the need to custom map it.
Why is this needed?
I am using Opencode, an AI coding agent CLI.
In Opencode, Shift+Enter is used to create a new line in the prompt window without submitting the message.
Because Warp intercepts Shift+Enter to handle its own input editor, the keystroke never reaches the Opencode process, or it submits the command prematurely.
Other terminals (like iTerm2 or Alacritty) allow remapping Shift+Enter to send raw hex codes, which fixes this compatibility issue. Warp currently lacks a "Send Hex Code" action in the Keyboard Shortcuts settings.
Steps to reproduce
Install Opencode (curl -fsSL https://opencode.ai/install | bash or bun add -g opencode-ai).
Run opencode in Warp.
Type a prompt and press Shift+Enter to add a new line.
Result: Warp acts on the key (often submitting the command) instead of passing the new line signal to the Opencode TUI.
Reacted by Mian Khalid, Raed, Eric Bizet, Alton Johnson, OSCP, OSCE, Damien Lecan, Dvir Chikvashvili, Dominik Bura, Paskahlis Anjas, Robin Genz, Mateus De Lima and 30 more
Reacted by Emman Nelson, ainexxo-master, Alton Johnson, OSCP, OSCE, Han.Z, Zeng Xian, Piotr Varaksin, Robin Genz, molmdl, Max Kirschning, Fabio and 2 more
Reacted by Mian Khalid, Eric Platon, YDKD and Flavio Silva
Reacted by Alton Johnson, OSCP, OSCE, Matthias Vogel, Antoine Maitre, Max Kirschning, Fabio and marcogalileo
changed the title [-]Can't get shift+enter to produce new line in Opencode[/-][+]Feature: Allow custom keybindings to send raw hex codes (e.g., \033OM for Shift+Enter) / OpenCode SHIFT+ENTER Fix.[/+]on Jan 20, 2026
changed the title [-]Feature: Allow custom keybindings to send raw hex codes (e.g., \033OM for Shift+Enter) / OpenCode SHIFT+ENTER Fix.[/-][+]Feature: Allow custom keybindings to send raw hex codes / OpenCode SHIFT+ENTER Fix.[/+]on Jan 20, 2026
Any way to get this fixed? will likely have to stop using Warp as a result
Quick fix, not to my knowledge. I tried exploring my options with different terminals and unfortnately Warp seemed like the most polished one. Even, tho I don't touch any of the AI features.
I tried to get any of the meta+return to work by hacking the opencode config key binds AND the Warp config Key bindings to use the same thing or different things etc. But nothing worked that I tried (cmd+, option+ etc) .. Just FYI. Would be nice to have a generic solution to pick the version of meta+return / enter wanted for a newline to be passed..
Hi all, thanks for your patience. The latest version of Warp (v0.2026.02.04.08.20.stable_02) now has support for the Kitty keyboard protocol, which should address this issue. I'm going to close this out but please file an issue if you see any bugs. Thanks!
Reacted by Mian Khalid, cometlj and Mateusz Komarnicki
Hey all, the latest version of Warp now has support for the Kitty keyboard protocol, which addresses this issue. Thanks for your patience here and let me know if you see any issues!
Activity
mynameistito commentedon Jan 17, 2026
Related Issues:
anomalyco/opencode#8038
anomalyco/opencode#4997
fangwangme commentedon Jan 19, 2026
It's disgusting to hijack such action. Please don't change universal behaviors.
miankhalid commentedon Jan 19, 2026
facing the same issue and +1 for a fix. (on MacOS)
mynameistito commentedon Jan 19, 2026
Glad to see it's not an isolated issue!
yesacarlosm commentedon Jan 19, 2026
ctrl + jis the way on unix based systems[-]Can't get shift+enter to produce new line in Opencode[/-][+]Feature: Allow custom keybindings to send raw hex codes (e.g., \033OM for Shift+Enter) / OpenCode SHIFT+ENTER Fix.[/+][-]Feature: Allow custom keybindings to send raw hex codes (e.g., \033OM for Shift+Enter) / OpenCode SHIFT+ENTER Fix.[/-][+]Feature: Allow custom keybindings to send raw hex codes / OpenCode SHIFT+ENTER Fix.[/+]m4ttyk commentedon Jan 24, 2026
Same in my Warp. Claude Code handles it well out of the box, though.
Btw,
input_delete_linealso doesn't work in Warp (on MacOS)jamesblackwell commentedon Jan 27, 2026
Any way to get this fixed? will likely have to stop using Warp as a result
mynameistito commentedon Jan 27, 2026
Quick fix, not to my knowledge. I tried exploring my options with different terminals and unfortnately Warp seemed like the most polished one. Even, tho I don't touch any of the AI features.
Raising your voice in their Discord: https://discord.com/invite/warpdotdev or Slack which I think is accessable via the Terminal, might also assist. I've reached out in both places and haven't heard anything yet, to my knowledge.
edit: added discord and slack mentions
tl-sjmcdowall commentedon Feb 2, 2026
I tried to get any of the meta+return to work by hacking the opencode config key binds AND the Warp config Key bindings to use the same thing or different things etc. But nothing worked that I tried (cmd+, option+ etc) .. Just FYI. Would be nice to have a generic solution to pick the version of meta+return / enter wanted for a newline to be passed..
mynameistito commentedon Feb 3, 2026
Huge news regarding this issue.
Warp Eng on Slack
alokedesai commentedon Feb 6, 2026
Hi all, thanks for your patience. The latest version of Warp (
v0.2026.02.04.08.20.stable_02) now has support for the Kitty keyboard protocol, which should address this issue. I'm going to close this out but please file an issue if you see any bugs. Thanks!3 remaining items
alokedesai commentedon Feb 8, 2026
Hi all, unfortunately we had to roll this back due to it regressing some pretty core neovim flows. I'll ping back as soon as it's rolled forward.
cometlj commentedon Feb 9, 2026
how can I rollback to the version v0.2026.02.04.08.20.stable_02 ? anyone help?
cometlj commentedon Feb 11, 2026
I managed to get the download link, the
shift+enter-> insert the newline func comes back!soundstep commentedon Feb 20, 2026
Very frustrating, what's the plan to add the shift+enter back?
cometlj commentedon Feb 20, 2026
can use the
shift+enterin versionv0.2026.02.04.08.20.stable_02, you can trychipit24 commentedon Feb 20, 2026
I just ended up using Hammerspoon to map the shortcut I needed to ⌃+j when my terminal was focused.
alokedesai commentedon Mar 9, 2026
Hey all, kitty keyboard protocol support (which gets shift-enter to work in opencode) is now rolled out our Preview build: https://warp.dev/download-preview
It should be out in our Stable build this week assuming there are no issues.
selahattinunlu commentedon Mar 12, 2026
Yay!!! I tried the preview now. It works fine. Thank you so much @alokedesai 🎉
alokedesai commentedon Mar 20, 2026
Hey all, the latest version of Warp now has support for the Kitty keyboard protocol, which addresses this issue. Thanks for your patience here and let me know if you see any issues!
flavio1110 commentedon Mar 25, 2026
Same here! It works fine in the latest version.
romanwozniak commentedon Apr 16, 2026
With the added KKP support, Shift+Enter issue is resolved. But it is still impossible to use Cmd+Left/Rigth, Cmd+Backspace, and Cmd+Shift+Left/Right.