›_ Codex Issues
Codex Issues / #27918

Codex Desktop still sends messages with Enter after configuring a custom send shortcut

Open 💬 3 comments Opened Jun 12, 2026 by itbencn
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What happened?

Codex Desktop supports customizing the keyboard shortcut used to send a message. However, even after configuring a custom send shortcut, the app still appears to force Enter to send the message.

There is also another Codex app setting:

Require Ctrl + Enter to send long text prompts When enabled, multi-line prompts require Ctrl + Enter to send.

After enabling this setting, the same behavior still occurs: Enter can still act as a send shortcut in cases where it should no longer be forcibly bound.

Expected behavior

After the user configures a custom send shortcut, Codex Desktop should respect that configuration and should not keep Enter forcibly bound as the default send shortcut.

If the user enables the setting that requires Ctrl + Enter for long text prompts, pressing Enter should insert a newline or otherwise follow the configured editing behavior instead of sending the message unexpectedly.

Why this matters

Users who customize the send shortcut usually do so to avoid accidentally sending incomplete prompts, especially while composing multi-line text. Keeping Enter forcibly bound makes the custom shortcut setting less reliable and can cause accidental sends.

Suggested behavior

  • The configured send shortcut should be the only active send shortcut unless the user explicitly enables additional shortcuts.
  • Enter should not send messages once the user has chosen a different send shortcut.
  • The "Require Ctrl + Enter to send long text prompts" setting should consistently prevent plain Enter from sending multi-line prompts.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #26460

Powered by Codex Action

Motoharu-Kataoka · 13 days ago

I can reproduce this issue on the Windows desktop app in Chat mode, and I found a specific state transition that may help isolate the cause.

Environment

  • Product: ChatGPT/Codex desktop app
  • Surface: Chat mode
  • Platform: Windows
  • Tested: August 15, 2026 (JST)
  • General > Send shortcut: Always Ctrl + Enter
  • Keyboard Shortcuts > Send message: Ctrl + Enter

I reproduced the behavior both with Japanese IME enabled and with the IME completely disabled using ordinary ASCII input.

Steps to reproduce

  1. In General settings, set Send shortcut to Always Ctrl + Enter.
  2. In Keyboard Shortcuts, assign Send message to Ctrl + Enter.
  3. Open a new Chat.
  4. Type a and press plain Enter several times.
  5. In the initial composer, plain Enter correctly inserts newlines.
  6. Send the initial message using Ctrl + Enter.
  7. Wait for the first assistant response.
  8. Type a in the follow-up composer.
  9. Press plain Enter.

Actual behavior

After the first assistant response, plain Enter immediately submits the message instead of inserting a newline.

From that point:

  • Enter submits the message.
  • Shift + Enter inserts a newline.
  • Ctrl + Enter remains available as the configured send shortcut.
  • Both settings screens still show Ctrl + Enter; the configuration itself has not visibly changed.

This also reproduces with the IME completely disabled and ASCII input, so it does not appear to depend on IME composition or conversion confirmation.

Expected behavior

With Send shortcut set to Always Ctrl + Enter, and Send message explicitly assigned to Ctrl + Enter:

  • Plain Enter should consistently insert a newline.
  • Ctrl + Enter should submit the message.
  • The behavior should remain the same between the initial composer and all follow-up composers in the same Chat.

Additional observation

The only consistent trigger I have identified is receiving the first assistant response.

Before the first turn, the configured shortcut works correctly. After the first response, the follow-up composer behaves as though the default Enter = send binding has been restored.

This may indicate that the follow-up composer is not inheriting the current send-shortcut configuration. That is only a hypothesis based on the reproducible UI behavior.

Related Windows report: #24049.

2811755043-bot · 7 hours ago

Still reproducible on the latest Windows desktop app available on August 28, 2026.

Environment

  • Product: ChatGPT/Codex desktop app
  • Platform: Windows 10
  • Context: existing multi-turn chat
  • General > Send shortcut: Always Ctrl + Enter

What I observed

  1. Updated the desktop app to the latest available version (the update took about 30 minutes).
  2. Restarted the app.
  3. Toggled the send-shortcut setting away and then back to Always Ctrl + Enter.
  4. Returned to an existing chat and typed a follow-up message.
  5. Pressed plain Enter.

Actual behavior

  • Plain Enter immediately submits the message.
  • Shift + Enter inserts a newline.
  • The settings UI still shows Always Ctrl + Enter.

Expected behavior

  • Plain Enter should insert a newline.
  • Ctrl + Enter should submit the message.

This confirms that the configured send behavior is still not being respected in the current Windows desktop build, even after updating and restarting.