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

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.