codex freezes when queued message is reached/begun, with multiple windows open.

Open 💬 3 comments Opened Apr 21, 2026 by mattroz22

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Right now i have 3 codex windows open, each working in a differentnt project folder. When I queue a message in a thread, and it gets to that message turns, it creates multiple messages of the same message and freezes on thinking. the solution is to quit the app and it fixes itself. odd. I love Codex though, excellent job thank you so much it's truly a revolutionary tool.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#17285
#17876
#18155

Powered by Codex Action

mattroz22 · 4 months ago

its similar to 2, but it freezes and i have to quit the app

EthanSK · 4 months ago

Adding another data point here because this sounds like the same bug family I'm hitting.

For me, queued messages are unreliable and can break the app when the queued message is finally sent. Instead of cleanly sending the queued prompt once, Codex can duplicate the queued message / duplicate work and the app ends up in a broken state.

The core symptom from my side is:

I queue a message while Codex is busy
when Codex gets to that queued message, things go wrong instead of running normally
the queued message can be sent more than once / duplicate behavior appears
the app effectively breaks at that point

If it helps triage, this feels very close to the broader queued-message bugs where queued prompts behave incorrectly or get replayed instead of being processed exactly once.