Settings ignored: Require CMD + enter for long prompts, Follow-up behavior
Open 💬 2 comments Opened Apr 11, 2026 by thebriancurtis
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.409.20454 (1462)
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
The "Require CMD + enter to send long prompts" and "Follow-up behavior" settings are ignored.
What steps can reproduce the bug?
Follow-up behavior:
- Set to "Queue"
- Submit prompt
Require CMD + enter to send long prompts:
- Set to enabled
- Submit a long prompt with just pressing enter.
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I am seeing the same regression in the Codex desktop app on Windows.
My local Codex desktop config has
followUpQueueMode = "queue", but follow-up messages still appear to steer the active run rather than being queued as the next turn. After updating Codex, I still do not see the previous UI affordance that let me choose between steering the current run and sending a sequential follow-up.This is disruptive because it makes it easy to accidentally redirect a long-running task instead of adding the next instruction after the current turn completes. A reliable queue/steer choice, or at least honoring
followUpQueueMode = "queue", would be very useful.Environment observed locally:
OpenAI.Codex_26.623.13972.0_x64__2p2nqsd0c76g0codex-cli 0.136.0This also appears related to #17285.