Repository navigation
Option+Up arrow does not edit queued message #14213
Description
What version of Codex CLI is running?
0.114.0-alpha.1
What subscription do you have?
Pro
Which model were you using?
gpt-5.4
What platform is your computer?
macOS
What terminal emulator and version are you using (if applicable)?
iTerm
What issue are you seeing?
I can no longer edit / de-queue queued messages
What steps can reproduce the bug?
- While codex is doing some work, enter a message and hit return (i.e. to send immediately as a steer)
- It tells you the message has been queued and will be sent after the current turn
- You decide to edit the message, option+up-arrow puts the message back into the prompt BUT does not remove it! You continue to see it in the queue.
What is the expected behavior?
I expect it to be removed from the queue / pending messages list
Additional information
No response
Activity
github-actions commentedon Mar 10, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Mar 10, 2026
You said "no longer". Do you suspect this is a regression? If so, what is the last version where this worked for you?
miraclebakelaser commentedon Mar 10, 2026
You were only allowed to edit queued messages (tabbed messages), not steering messages. I think this most recent change to the presentation of steering messages (making them look queued) was to make clear the insertion point of the steering message.
guidedways commentedon Mar 11, 2026
Yes I may have conflated the two - indeed, I think this is new, steered (and queued) messages seem to be handled differently during an ongoing-tool call (which is a welcomed change!) however since it's queued, it should be no different from a normal queued message; we should be allowed to de-queue it / edit it while it's still waiting to be processed. In my case some of these tool calls are part of a long-running custom skill, and so if I've made an error / changed my mind, there seems to be no way to dequeue / edit the message if it's a pending steer.
miraclebakelaser commentedon Mar 11, 2026
Agreed. I enjoy the added clarity, but now seeing how long some of those steering messages can stay queued, I also want to be able to edit them.
EricBlanquer commentedon Sep 2, 2026
I’m seeing the same issue with the Up arrow.
It recalls the last queued message and lets me edit it, but pressing Enter adds the edited version as a new queued message instead of replacing the original one.
mekineer-com commentedon Oct 8, 2026
Sometimes a steering message is no longer relevant by the time Codex gets to it, but there's no way to take it back. We built a fix to recall the queued message to the input field so it can be edited or discarded.
Source code.
mekineer-com commentedon Oct 8, 2026
The code is now published: https://github.com/mekineer-com/codex/tree/aster/pending-steer-recall
mekineer-com commentedon Oct 9, 2026
Updated the implementation to use the existing Alt+Up shortcut and composer restoration path. Recall now follows submission order across Tab-queued and Enter-sent messages, rather than prioritizing one queue.
For connected steering messages, removal is atomic in the active turn’s existing input queue; the message returns to the input field only after the server confirms withdrawal.