Codex desktop app only offers Local when continuing a visible Cloud task
What happened?
In the Codex desktop app on macOS, I can see a Codex Cloud task under a project/environment, but when I try to continue it from the desktop app composer, the only available destination is Local. There is no Cloud option.
The composer text says:
Create a new local task that references this cloud task
and the destination dropdown shows only:
Continue in
- Local
This makes it look like the desktop app can view/reference the cloud task, but cannot continue it in Cloud.
Expected behavior
When viewing a Codex Cloud task in the desktop app, I expected to be able to continue/follow up in the same Cloud environment, or at least choose Cloud in the destination selector.
Actual behavior
Only Local is offered. Continuing from the desktop app creates a local task that references the cloud task instead of continuing the cloud task in Cloud.
Evidence / checks
- The same Cloud environment is visible and works in the web app.
- The desktop app sidebar shows the project/environment and the Cloud task.
codex cloud liston the same machine can see the task successfully.- CLI output shows the task as
[READY], environment labelrose, with no diff. codex cloud --helpis available locally.
Redacted CLI/task detail:
codex-cli 0.128.0
codex cloud list
https://chatgpt.com/codex/tasks/task_e_[redacted]
[READY] Hello
rose • ~20m ago
no diff
Environment
- Platform: macOS
- Surface: Codex desktop app
- CLI version:
codex-cli 0.128.0 - Cloud environment label:
rose - Branch shown in web app:
main
Related/possibly adjacent
I found a similar/adjacent issue about desktop app Cloud task availability, but this case is different because Cloud auth works and the task is visible in both the web app and CLI; only desktop follow-up routing is limited to Local.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗