`Tab` for queue message after a turn is ended does nothing

Resolved 💬 3 comments Opened Feb 9, 2026 by lgo Closed Apr 22, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.99.0-alpha.6

What subscription do you have?

Pro

Which model were you using?

n/a

What platform is your computer?

Darwin 25.2.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Cursor

What issue are you seeing?

When a turn finishes, you can't Tab for queueing a message anymore. This is a bit of a UX rough edge, as I'll often be queuing up messages along the way for a prompt progressing and once it's done then I'll hit Tab and wonder why nothing happens.

I typically use this, over preamble steering, as it'll be multiple stacked changes that are follow-ups unrelated to the core ask.

(Sorry if bug isn't the right category! This is more like a UX issue)

What steps can reproduce the bug?

n/a

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

lassegit · 6 months ago

I have the same issue.

oxysoft · 5 months ago

Linking #14677 here because it feels like the higher-order queue UX that sits above this ticket.

This issue is about preserving Tab queueing after a turn ends. #14677 asks for the queued-message stack itself to become a first-class surface: navigate queued messages with Alt+Up/Down, drop into editing on release (or via a modal fallback), and eventually reorder them.

If Codex keeps investing in queued follow-up prompts, the queue should probably become a real operable object rather than a narrow convenience.

etraut-openai contributor · 4 months ago

I think this was fixed long ago, so closing the ticket.