Plain Enter sends follow-up messages despite “Always Ctrl + Enter” send shortcut on Windows

ChatGPT Bugs
,
1

Environment

  • Product: ChatGPT/Codex unified desktop app
  • App version: 26.825.4187.0
  • Surface: Chat mode
  • Platform: Windows 11 Home
  • Windows version: 25H2
  • Application language: Japanese
  • Tested: August 29, 2026 (JST)

ChatGPT settings

General > Composer:

  • Send shortcut: Always Ctrl + Enter
  • Follow-up Behavior: Sender

Keyboard Shortcuts:

  • Send message: Unassigned
  • Send message in background: Ctrl + Enter

Steps to reproduce

  1. Set General > Composer > Send shortcut to Always Ctrl + Enter.
  2. Open a New Chat.
  3. Type text in the initial composer.
  4. Press plain Enter.
  5. Confirm that Enter correctly inserts a newline.
  6. Press Ctrl + Enter to submit the first message.
  7. Wait for the assistant’s response.
  8. Type another message in the follow-up composer.
  9. Press plain Enter.

Actual behavior

In the initial composer of a new chat, the configured behavior works correctly:

  • Plain Enter inserts a newline.
  • Ctrl + Enter submits the message.

However, after the first assistant response, the behavior changes in the follow-up composer:

  • Plain Enter submits the message.
  • Shift + Enter inserts a newline.
  • Ctrl + Enter can also submit the message.

The setting still shows Always Ctrl + Enter and has not visibly changed.

Restarting the PC does not resolve the issue.

This indicates that, in the current Windows desktop build, the configured send behavior is not consistently respected between the initial composer and subsequent follow-up composers.

The behavior appears as if the follow-up composer restores the default Enter = Send binding after the first assistant response, while the configured Ctrl + Enter behavior remains active.

Expected behavior

With Send shortcut = Always Ctrl + Enter:

  • Plain Enter should consistently insert a newline and should never submit the message.
  • This behavior should apply while composing all types of text, including multi-line text and Markdown.
  • Ctrl + Enter should consistently submit the message.
  • The behavior should remain identical between the initial composer and every subsequent follow-up composer within the same chat.
  • Receiving an assistant response should not change or override the configured send shortcut.

This is particularly important when composing structured or multi-line prompts, because an unexpected plain-Enter submission can send an incomplete message.

Additional product suggestion

Separately from the bug above, I would also suggest considering Ctrl + Enter as the default send behavior, with plain Enter inserting a newline.

For an application frequently used to compose long, structured, and Markdown-formatted prompts, using plain Enter for text editing and requiring Ctrl + Enter for intentional submission would reduce accidental sends.

2

Thanks for the clear repro steps. You’ve already enabled the right setting, so the follow-up composer behavior needs a closer look. Please share this with Support, including your app version: https://help.openai.com/en/articles/6614161. We’ll also pass along the default-shortcut suggestion.