{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiatpc5yhf6vc55zbqydlrwqs4hwcccbnln72yvfe44oheje2h27mq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mjr4pa7jhrb2"
  },
  "path": "/t/feature-request-allow-a-fixed-ctrl-enter-send-shortcut-in-codex-chat/1379225#post_2",
  "publishedAt": "2026-04-18T09:15:04.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "GitHub OpenAI Codex issues",
    "searching",
    "github.com/openai/codex",
    "Make ENTER insert newline in Codex TUI input (send on Ctrl+Enter instead)",
    "smileBeda",
    "Codex features are prioritized by votes in GitHub issues tab",
    "Codex",
    "Source"
  ],
  "textContent": "Welcome to the forum!\n\nYou are welcome to post feature request here however the official place to request codex enhancements is the GitHub OpenAI Codex issues tab and use the label `enhancement`\n\nIn searching the issues with `enhancement` find:\n\ngithub.com/openai/codex\n\n####  Make ENTER insert newline in Codex TUI input (send on Ctrl+Enter instead)\n\nopened 12:07PM - 18 Feb 26 UTC\n\n\n\n          smileBeda\n        \n\nenhancement  TUI\n\n### 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_\n\n* * *\n\nIf 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`.\n\n* * *\n\nAlso see:\n\nCodex features are prioritized by votes in GitHub issues tab Codex\n\n> 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 Note: In GitHub feature request…",
  "title": "Feature Request: Allow a fixed Ctrl+Enter send shortcut in Codex chat"
}