Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Allow queued prompts after queued /new [4 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19151•Fetched 2026-04-24 05:59:48
View on GitHub
Comments
4
Participants
2
Timeline
15
Reactions
0
Author
JoeRoddyJoeRoddy
Participants
etraut-openaietraut-openaiJoeRoddyJoeRoddy
Timeline (top)
labeled ×5commented ×4unlabeled ×3mentioned ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.123.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.4

What platform is your computer?

Darwin 25.4.0 arm64 arm

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

WarpTerminal 0.2026.04.15.08.45.02

What issue are you seeing?

Codex CLI lets users queue prompts with Tab while the current turn is running. Queued prompts normally run after the current turn completes.

If /new is queued, and additional prompts are queued after /new, the queued /new runs and creates a new chat, but the remaining queued prompts after /new are dropped. They do not run in the newly created chat and do not remain visible/recoverable in the queue.

This loses user-entered prompts without an explicit warning.

What steps can reproduce the bug?

  1. Start Codex CLI.
  2. Submit a prompt that keeps the current turn running long enough to queue follow-up input.
  3. While the current turn is running, type /new and press Tab to queue it.
  4. Type one or more additional prompts and press Tab to queue them after /new.
  5. Wait for the active turn to complete.
  6. Observe that /new runs and creates a new chat.
  7. Observe that the prompts queued after /new are dropped instead of running after the new chat is created.

What is the expected behavior?

Queued prompts after /new should not be silently dropped.

Expected behavior should be one of:

  • /new creates the new chat, then subsequent queued prompts run in that new chat in order.
  • Or Codex rejects/warns when queuing prompts after a queued /new, making clear that /new is a queue boundary.
  • Or Codex preserves the remaining queued prompts and lets the user decide what to do with them.

In all cases, user-entered queued prompts should remain recoverable unless explicitly discarded.

Additional information

I searched open issues and did not find an exact duplicate. Related but not identical issues include:

  • #17285 queued prompts behave like steer prompts / multiple queued prompts sent simultaneously
  • #13078 sending a message near the end of a response does not queue it
  • #15842 pending queued/steer input can get stuck
  • #13892 queued follow-ups mixed with pending steer state
  • #15137 control slash commands during active runs

extent analysis

TL;DR

The issue can be mitigated by modifying the queue handling logic to either run queued prompts after /new in the new chat or provide a warning when queuing prompts after a queued /new.

Guidance

  • Review the queue handling logic to identify why queued prompts after /new are being dropped.
  • Consider implementing a check to warn users when queuing prompts after a queued /new, making it clear that /new is a queue boundary.
  • Explore the possibility of running queued prompts after /new in the newly created chat, ensuring that user-entered prompts are not lost.
  • Investigate related issues (#17285, #13078, #15842, #13892, #15137) to see if they provide insight into the queue handling logic and potential solutions.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The solution may require changes to the Codex CLI's queue handling logic, which could have implications for other features and functionality.

Recommendation

Apply a workaround by modifying the queue handling logic to provide a warning when queuing prompts after a queued /new, as this approach is more straightforward and less likely to introduce new issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#mixed precision#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Allow queued prompts after queued /new [4 comments, 2 participants]