Cloud task started in Codex Desktop disappears after navigating to another thread

Open 💬 2 comments Opened Jul 27, 2026 by edwardsanchez
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.721.41059

What subscription do you have?

Pro

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

A Codex Cloud task started from the macOS desktop app disappears from the app after navigating to another thread.

The cloud task itself is not lost. It remains available through its direct ChatGPT Codex task URL, and codex cloud list returns it with status READY. However, it is absent from:

  • Recents
  • the associated project/environment in the sidebar
  • projectless chats
  • any visible Cloud or Remote task-history surface in the desktop app

This creates a dead end: the desktop app can create the cloud task, but after leaving it there is no apparent way to find or reopen it from the app.

What steps can reproduce the bug?

  1. Open Codex Desktop on macOS.
  2. Start a new chat.
  3. Select a Codex Cloud environment/repository as the execution environment.
  4. Submit a prompt so that the cloud task is created and opened in the desktop app.
  5. Navigate to a different existing thread.
  6. Look for the cloud task in Recents, the related project/environment, and the rest of the sidebar.
  7. Observe that the cloud task is nowhere in the desktop app.
  8. Run codex cloud list or open the task URL on chatgpt.com/codex/tasks/task_e_[redacted].
  9. Observe that the task still exists and is complete/ready in Codex Cloud.

CLI version on the same machine: codex-cli 0.144.6.

What is the expected behavior?

A cloud task created from Codex Desktop should remain discoverable and reopenable from Codex Desktop after navigating away.

It could appear in Recents, under its cloud environment/repository, or in a dedicated Cloud/Remote task-history section. At minimum, the app should retain a durable link to every cloud task that it creates.

Additional information

The task had:

  • a normal task_e_... cloud task ID
  • a valid direct URL
  • status READY in codex cloud list
  • no diff, which should not affect whether the task remains discoverable

This appears distinct from #29694. In that report, a cloud task is visible in the desktop app but can only be continued locally. In this case, the cloud task disappears from the desktop app entirely after navigating away.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

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

  • #34754

Powered by Codex Action

JuliaWinn · 5 days ago

Still reproducing for me as of 2026-08-18.

Environment:

  • ChatGPT/Codex Desktop 26.727.51351 (build 6119)
  • macOS 26.5 (25F71)

Observed behavior:

  1. Start a chat/task and leave it running.
  2. Navigate away from that chat.
  3. The in-progress chat disappears from the visible chat/task list, so there is no obvious way to reopen or monitor it while it is running.
  4. In some cases, after the task finishes, refreshing causes the chat to reappear.

This makes the task look lost even though it appears to continue running in the background. The current release therefore has not fully resolved this behavior for me.