ChatGPT/Codex MacOS App CMD+Enter/Return key settings DOESN'T WORK
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.825.41651
What subscription do you have?
Plus
What platform is your computer?
MaxOS 26.3 (Darwin 25.5.0 arm64 arm)
What issue are you seeing?
Under settings-general-composer-'SEND SHORTCUT': CMD+Enter Always. -> Settings only apply to first initial message, but not the follow ups. After first message, rest of the message would fire after one Enter key.
The inconsistance mess the heck out of me sometimes i have to do CMD+Enter and sometimes one Enter key would send half-finished message out.
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a04e7a-d935-77d1-899b-058b97c7dec1
What is the expected behavior?
Steps to reproduce bug:
on a MacOS device, in Codex/ChatGPT app, change settings to CMD+Enter always (settings-general-composer-'SEND SHORTCUT': CMD+Enter Always), and send out a normal chat message in chatgpt. You may see that you have to do (CMD+ENTER). Then send another message under the same conversation. You may see now only hitting "ENTER" would fire the message, not switch to next line.
On web version, i have changed "send" keyboard shortcut to CMD+Enter. which works and helped.
But on the App version, I tried to change the keyboard shortcut "send" to CMD+enter, but it says "Focus floating quick chat" is using it, and there isn't a keyboard settings for "Focus floating quick chat"
What is the expected behavior?
Should be always "Enter" = next line, "CMD+Enter" = send.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through Settings > General > Composer > Send Shortcut and the floating quick chat shortcut on macOS. Trace how the send shortcut is applied to the initial message and follow-up messages; done means CMD+Enter always sends, Enter inserts a newline, and the shortcut conflict is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100