Allow 'cmd + enter' to send message permanently as an option

Open 💬 1 comment Opened Jun 4, 2026 by inspirepassion

What version of the Codex App are you using (From “About Codex” dialog)?

26.601.21317

What subscription do you have?

Plus plan

What platform is your computer?

Macbook Pro M3

What issue are you seeing?

Codex currently auto decide whether I can use 'enter' only or 'cmd + enter' to send message based on the message length.

I want permanently to use 'cmd + enter' to send message, but this mixed auto decision process really creates trust issue, like how long is long? I have to 'guess' before I decide to hit 'cmd + enter' or 'enter' only. 90% of my workflow is long multip paragraphs sentences, and I am really aginst this 'guessing' feeling every second I use Codex.

Right now, it's very awkward to mix up these:

1) use 'Shift + enter' to create the first multi line input
2) now you can use 'enter' to create multi line from now on
3) now you can use 'cmd + enter' to send the message.

Codex can totally allow permanent 'cmd + enter' to send message, such that users don't have to be so mindful about if I hit 'shift + enter' to create the first multi line message. You can totally erase the 'shift + enter', and users only need 'enter' to create new lines, and 'cmd + enter' to send message (user only need these two commands only in their daily work, instead of three)

Plz just allow 'cmd + enter' to be a permanent option for sending message.

What steps can reproduce the bug?

Setting -> General -> :

Require ⌘ + enter to send long prompts
When enabled, multiline prompts require ⌘ + enter to send

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗