Desktop Add to task freeze can trigger duplicate submissions after task acceptance

Open 💬 1 comment Opened Jul 17, 2026 by coolxll

I am filing this as a visibility and user-impact follow-up to #32033, not as a claim of a separate root cause. Please link or close it as a duplicate if #32033 remains the preferred canonical tracker.

Summary

When I use the official ChatGPT conversation reference / Add to task flow, the Codex Desktop UI can freeze immediately after submission even though the task has already been accepted and continues running remotely.

User impact

  • The conversation pane shows no response or trace.
  • The composer becomes unusable, while the Pet still indicates that the task is active.
  • Remote control/view shows that the task continues executing normally.
  • Without a durable task-accepted acknowledgement, I previously resubmitted the same task multiple times.
  • This caused duplicate tasks, wasted Team usage/quota and time, and a risk of multiple agents modifying the same workspace concurrently.

The issue is intermittent and appears specific to the Desktop ChatGPT conversation handoff/local conversation-rendering path. I have not observed the same failure mode in the CLI.

Expected behavior

The app should immediately expose a durable task identifier and acceptance state, continue showing task progress if the renderer fails, warn about repeated submission, and allow the UI to reattach to the already-running task without terminating it.

Environment

  • Codex App version: 1.2.35 (build 1.2.35)
  • macOS version: 26.5.2
  • Architecture: arm64
  • Subscription: Team
  • Approximate occurrence date: 2026-07-18

Related issues: #32033, #32117, and #32846.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗