Codex Desktop: Allow Ctrl+Enter to be disabled or reassigned independently of Enter
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Desktop app on Windows, installed package version 26.903.8094.0.
What feature would you like to see?
Please make the built-in Ctrl+Enter composer shortcut independently configurable in the keyboard shortcut settings, including an option to disable it completely.
I use Enter to send normal messages and steer an active response. That behavior already works the way I want. I want to disable Ctrl+Enter, or assign its action to a different key combination, while keeping Enter working exactly as it does now.
Expected behavior:
- Enter continues to send messages and steer according to the current preferences.
- Disabling Ctrl+Enter prevents that key combination from submitting a message or triggering a follow-up action.
- Reassigning the action removes the original Ctrl+Enter binding unless it is explicitly retained as an additional shortcut.
Additional information
Related: https://github.com/openai/codex/issues/27918, which reports that Enter still sends after configuring a custom send shortcut. This request concerns keeping Enter enabled while independently disabling or reassigning Ctrl+Enter.
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 locating the Desktop app's keyboard shortcut settings and the composer handling for Enter and Ctrl+Enter. Verify the current preferences and related issue #27918, then define done as independently disabling or reassigning Ctrl+Enter while preserving Enter's existing behavior and removing the original binding unless explicitly retained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100