Cant message my chats anymore without new queue #48550

Activity

1. eah3699

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Sep 26, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   agentIssues related to the core agent loopIssues related to the core agent loop

   on Sep 26, 2026
3. github-actions commented on Sep 26, 2026

   

   github-actionsBot

   on Sep 26, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Message Queue bug #48516

   Powered by Codex Action
4. Tetsuya-Matsudo commented on Sep 29, 2026

   

   Tetsuya-Matsudo

   on Sep 29, 2026 – with ChatGPT Codex Connector

   More actions

   Additional reproduction on Windows desktop, Codex/ChatGPT app 26.924.22138 (build 11645, production channel), observed on 2026-09-29.

   • Since a recent desktop UI update, follow-up prompts repeatedly appear to remain in the queue.
   • In one reproduction, the app showed the thread as actively working, and the thread history confirmed that the queued user prompt had already started a new turn, while the same prompt was still visible in the queued-message strip.
   • After the trash icon on that apparent stale queue row was clicked, the prompt appeared in the transcript while the turn was already running. I cannot establish that the click caused dispatch; this may be a stale UI state or timing/race issue.
   • Switching to another chat and back, and fully restarting the desktop app, did not resolve the recurring behavior.

   Expected: once a queued follow-up begins its turn, the queue indicator should clear and the prompt should be visible in the transcript. A user should not have to guess whether a prompt is queued, executing, or removed.

   This is especially risky for tasks that change external state, because an apparently stuck prompt may already be running and a resend could duplicate the action.

   Related report: #48516. No screenshots, session transcripts, logs, project names, or personal data are attached.