# Feature Request: Allow a fixed Ctrl+Enter send shortcut in Codex App chat **URL:** \ **Category:** Codex\ **Created:** [April 18, 2026, 2:27am UTC](https://community.openai.com/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-app-chat/1379225 "2026-04-18T02:27:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![decoupling](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@decoupling](https://community.openai.com/u/decoupling)\ **Post date:** [April 18, 2026, 2:27am UTC](https://community.openai.com/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-app-chat/1379225/1 "2026-04-18T02:27:42Z")
### **Within App, not CLI.** * * * I’d like to request an option in Codex settings to make **Ctrl+Enter always send** and **Enter always insert a newline**. Right now, the send behavior changes depending on whether the input is single-line or multi-line: - when the message is a single line, pressing **Enter** sends immediately - when the message becomes multi-line, the shortcut changes and **Ctrl+Enter** sends instead This inconsistency is easy to trigger by accident, and I often send messages before I intend to. My typical workflow is writing detailed prompts and task descriptions, so most of my inputs are multi-line. Because of that, I strongly prefer a consistent editing model where: - **Enter** always creates a new line - **Ctrl+Enter** always sends - this behavior can be enabled as a setting and stays fixed regardless of whether the current text is one line or multiple lines A configurable option like this would make drafting long prompts much safer and more predictable. Thanks. ---
**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\ **Post date:** [April 18, 2026, 9:15am UTC](https://community.openai.com/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-app-chat/1379225/2 "2026-04-18T09:15:04Z")
Welcome to the forum! You are welcome to post feature request here however the official place to request codex enhancements is the [GitHub OpenAI Codex issues](https://github.com/openai/codex/issues) tab and use the label `enhancement` In [searching](https://github.com/openai/codex/issues?q=is%3Aissue%20state%3Aopen%20label%3Aenhancement%20ctrl%20enter) the issues with `enhancement` find: > > > \### What variant of Codex are you using? > > CLI > > \### What feature would you like t…o see? > > \### Summary > > Currently, the Codex CLI/TUI sends the prompt on \`ENTER\` and inserts a newline on \`Ctrl + J\`. While this matches traditional terminal behavior, the Codex TUI functions primarily as a multiline prompt editor rather than a classic shell. > > This keybinding choice conflicts with modern text-editing conventions and frequently leads to accidental submission of incomplete prompts. > > \--- > > \### Problem > > In most contemporary tools (IDEs, chat interfaces, documentation tools, browsers, etc.): > > \- \`ENTER\` inserts a newline > \- \`Ctrl + Enter\` submits content (or, alternatively, \`CMD + Enter\`) > > The Codex TUI reverses this expectation: > > \- \`ENTER\` submits > \- \`Ctrl + J\` inserts newline > > This creates several usability issues: > > \- Strong mismatch with established typing muscle memory > \- Frequent accidental submission of unfinished prompts > \- Cognitive friction when switching between Codex and other tools > \- \`Ctrl + J\` is non-standard and unintuitive for multiline entry > > In practice, this results in a high rate of unintended prompt submission. > > \--- > > \### Proposed Change > > Adopt a text-editor-oriented interaction model: > > \- \`ENTER\` → Insert newline > \- \`Ctrl + Enter\` or \`CMD + Enter\` → Submit prompt > > Alternatively, and MUCH BETTER - make this configurable: > > \- \*\*Terminal-style mode\*\* (current behavior) > \- \*\*Editor-style mode\*\* (proposed behavior) > \- \*\*Define custom bindings\*\* (let user choose their combinations) > > \--- > > \### Rationale > > The Codex TUI operates more like a structured prompt composition interface than a traditional command shell. Aligning keybindings with modern editor conventions would: > > \- Reduce accidental submissions > \- Improve workflow consistency > \- Lower cognitive load > \- Better match user expectations in AI prompt composition contexts > > This change would improve usability without affecting core functionality. > > \### Additional information > > \_No response\_ * * * If the matches what you seek then give the issue a thumbs up to let the OpenAI developers know this is important to you. If this does not match your desired request then look further or open a new issue with the label `enhancement`. * * * Also see: > [@Codex features are prioritized by votes in GitHub issues tab](https://community.openai.com/t/codex-features-are-prioritized-by-votes-in-github-issues-tab/1374249): > > FYI We prioritize feature requests based on upvotes from the community. If a feature request doesn’t get enough upvotes, we’ll close it. It’s therefore important for a feature request to have a clear and compelling title and description. We also recommend that feature requests focus on the problem statement rather than a solution. Describe the use case and what problem you’d like to see solved. There are often multiple ways to address a given problem. [Source](https://github.com/openai/codex/issues/11701#issuecomment-3898094375) Note: In GitHub feature request… ---
**Author:** ![merefield](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/merefield/32/14812_2.png) [@merefield](https://community.openai.com/u/merefield)\ **Post date:** [April 18, 2026, 9:37am UTC](https://community.openai.com/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-app-chat/1379225/3 "2026-04-18T09:37:20Z")
does this meaningfully change anything - how much is the LLM going to be swayed by a NL char? ie can the prompt really improve from adding NLs? I suppose it avoids having to cut and paste specifications from another text editor and you can then write them with headings directly inside the CLI? … just curious ---
**Author:** ![decoupling](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@decoupling](https://community.openai.com/u/decoupling)\ **Post date:** [April 18, 2026, 11:19am UTC](https://community.openai.com/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-app-chat/1379225/4 "2026-04-18T11:19:02Z")
Making the text more readable for humans is mainly for our own needs, and only secondarily for the use of AI ---
**Author:** ![merefield](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/merefield/32/14812_2.png) [@merefield](https://community.openai.com/u/merefield)\ **Post date:** [April 18, 2026, 3:23pm UTC](https://community.openai.com/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-app-chat/1379225/5 "2026-04-18T15:23:54Z")
Understood. My needs are more biased towards the AI (when coding)