Codex Desktop approval modal: Enter inserts newline in Other response despite Send hint

What version of the Codex App are you using (From "About Codex" dialog)?

Codex Desktop on Windows, Microsoft Store/AppX package:

• OpenAI.Codex_26.519.5221.0_x64__2p2nqsd0c76g0

What subscription do you have?

Unknown / not relevant.

What platform is your computer?

Windows, x64. Local OS version: Microsoft Windows 10.0.26200, build 26200.8457, Education edition.

What issue are you seeing?

In Codex Desktop, the sandbox / out-of-sandbox execution approval modal has a free-form "other" response path. When that free-text field is focused, pressing Enter inserts a newline instead of submitting the response.

This is surprising for two reasons:

1. The global Codex Desktop composer setting on this machine is configured so Enter sends and Shift+Enter inserts a newline.
2. The approval modal's bottom action row shows Skip and Send, and the Send action displays an Enter-key hint/glyph, which communicates that Enter should activate Send.

As a result, the modal behaves like a multiline text area even though both the app-level input setting and the modal's own UI hint point to Enter submitting. This appears to be a regression from recent desktop updates. I have not tested whether Ctrl+Enter submits, but the visible UI currently advertises plain Enter.

What steps can reproduce the bug?

1. In Codex Desktop on Windows, configure the message composer so Enter sends and Shift+Enter creates a newline.
2. Trigger a sandbox / out-of-sandbox execution approval prompt.

• For example, have Codex request a command that requires sandbox_permissions = "require_escalated".

1. In the approval modal, choose the free-form / "other" response option.
2. Type a short response into the free-text field.
3. Press Enter.

Observed result:

• A newline is inserted into the free-text field.
• The approval response is not sent.
• The modal remains open until Send is clicked or submitted by another shortcut.

What is the expected behavior?

When the free-form response field is focused in the approval modal:

• Enter should activate the modal's Send action, matching the visible Enter-key hint on the Send button and the global "Enter sends" composer setting.
• Shift+Enter should be the newline gesture if multiline input is supported in that field.

If the approval modal intentionally uses a different keyboard contract from the main composer, the button hint and documentation/settings UI should make that explicit instead of showing an Enter-key submit hint.

Additional information

I searched existing openai/codex issues and did not find an exact duplicate for this desktop approval-modal behavior.

Closest but not exact matches:

• #23227: asks for interactive editing of sandbox permission requests in the TUI, not the Desktop approval modal's Enter-to-submit behavior.
• #23536 / release notes for 0.133.0: fixed modified Enter handling in TUI plan questions, not this Desktop modal.
• #20580 and duplicates: TUI Shift+Enter / Alt+Enter newline regression, not the Desktop approval modal.
• #4212 / #11298 / #15169: approval persistence or repeated approval prompts, not the free-text field keybinding.

I did not find documentation saying the Desktop approval modal's free-form response field is intentionally multiline or exempt from the global Enter-to-send setting.