›_ Codex Issues
Codex Issues / #32373

Windows Desktop: archived remote task stays active and can freeze the entire system

Open 💬 0 comments Opened Jul 11, 2026 by Siermayde

Summary

On Windows, a ChatGPT/Codex Desktop remote task remains visibly active after being archived. The archived task continues to show “正在处理你的任务” (“Processing your task”) with an active stop control/spinner. While this task is present, the ChatGPT desktop app can make the entire computer unresponsive, including the mouse.

The same repository and workflow run normally through the Codex CLI, so this appears specific to the ChatGPT/Codex Desktop renderer/task-state lifecycle rather than the repository itself.

Environment

  • Platform: Windows
  • ChatGPT/Codex Desktop package observed locally: OpenAI.Codex_26.707.3748.0_x64__2p2nqsd0c76g0
  • Repository/project: Siermayde/CheatMenuPro
  • Branch: main
  • Remote task ID: task_e_6a51fa4b51d8832d9be3063c6978938b
  • Date observed: 2026-07-11
  • Codex CLI on the same machine: works normally and does not cause the system-wide freeze

Steps to reproduce

  1. Open the ChatGPT/Codex Desktop app on Windows.
  2. Create or open a task for the Siermayde/CheatMenuPro project on branch main.
  3. The task creation/processing fails or becomes unusable.
  4. Archive the task.
  5. Open the archived task again or refresh the task view.

Actual behavior

  • The archived task remains displayed as “正在处理你的任务” / “Processing your task”.
  • An active stop control and spinner remain visible.
  • Archive has no effective cleanup effect.
  • The task cannot be deleted through the normal archive/delete flow.
  • When this task is present in the desktop app, the whole Windows desktop can become unresponsive and the mouse may stop moving.
  • Force-ending the desktop app process is required to recover the computer.
  • Codex CLI on the same repository remains usable.

Local desktop logs also repeatedly referenced the remote route /remote/task/task_e_6a51fa4b51d8832d9be3063c6978938b, including remote-task lifecycle registration and a warning that no owner repository was found for the remote task.

Expected behavior

  • Archiving a remote task should stop active UI/task tracking and remove it from the active-processing state.
  • A stuck task should have a reliable cancel/stop path.
  • An archived task should be deletable through the documented archive/delete flow.
  • A stale remote task must not cause system-wide Windows UI/input freezing.
  • CLI and Desktop should not diverge into a desktop-only system freeze for the same project/task workflow.

Related issues

  • #25713: Windows Desktop repeatedly resumes an archived thread and freezes.
  • #25541: Windows Desktop archived conversations reappear after refresh/reconciliation.
  • #12852: Desktop threads remain stuck in Thinking and Stop is ineffective until the background process is force-killed.

Requested investigation

Please investigate:

  1. Whether the remote task remains active server-side after archive.
  2. Why the Desktop renderer continues to show an active stop state after archive.
  3. Whether the remote-task lifecycle/reconciliation loop can consume enough CPU or IPC resources to freeze Windows input.
  4. Whether a server-side cancel/delete operation is available for this task type.
  5. How users can recover without losing access to the project or killing unrelated Codex CLI sessions.

View original on GitHub ↗