Queued messages + internet issues messes up workflow significantly

Open 💬 0 comments Opened Jul 8, 2026 by mick-net

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.623.141536 • Released Jul 7, 2026

What subscription do you have?

Pro 20x

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Issue with queued messages in combination with internet issues ( stream disconnect -during an mobile hotspot issue).
The stream disconnect issue is not incorrect during internet issues, but the problem is that once the internet comes back, Codex starts working on the next queued message instead of finishing the previous request. This messes up the workflow significantly.

Reproduce by starting a normal chat, let codex work, meanwhile queue a next message. Then disconnect internet (to simulate e.g. hotspot issue). Codex shows reconnecting 1/5. However when the internet comes back it automatically starts working on the next queued message instead of the existing/previous message.

This messes up the workflow because i have to remove/edit the newly added message, and tell codex again to continue working on the previous message

What steps can reproduce the bug?

Feedback ID: 019e03ae-a84f-7fc3-8c52-e2a2ce08693d

What is the expected behavior?

expected that codex would first continue on the existing chat before working on the new queued message.

Additional information

_No response_

View original on GitHub ↗