[Windows][Codex Desktop] Cloud Recents threads cannot be archived and are absent from web

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

26.820.60940

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Two cloud-marked conversations remain in Recents, but both Archive and Delete fail every time. The entries cannot be removed from Codex Desktop.

A direct archive attempt through the app's task-management interface also fails with:

No Codex thread found for threadId: <redacted>
Hosts without a readable match: local

Local read-only diagnostics show that both entries still exist in the Desktop thread catalog with:

• source_kind = chatgpt
• conversation_origin = tpp
• a ChatGPT-host identifier rather than the local Codex host

The same conversations are not returned by the normal Codex task list, archived-task list, or ChatGPT web search. Opening their conversation IDs directly on ChatGPT redirects to the home page.

This looks like Desktop Recents is surfacing cloud/ChatGPT thread records that the archive and delete endpoints no longer recognize.

This is very similar to #40432, but that report concerns CLI-created threads on macOS. This case concerns cloud-marked ChatGPT-origin threads on Windows.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows.
2. In Recents, locate a conversation displaying the cloud icon ("Runs in the cloud").
3. Right-click the conversation and select Archive.
4. Codex displays Failed, and the conversation remains in Recents.
5. Select Delete for the same conversation; it also fails.
6. Repeat with a second cloud-marked conversation; the result is identical.
7. Search for either conversation in ChatGPT/Codex on the web; neither is found.

Two affected conversation IDs were confirmed locally but are redacted here for privacy. Their prefixes are 6a8e1f37-… and 6a8f763d-…. Full identifiers and narrowly filtered diagnostics can be provided privately if needed.

The affected conversations were trivial test conversations; token and context-window usage are not relevant.

What is the expected behavior?

Archive should remove the conversation from Recents and make it available under Archived conversations. Delete should remove it according to the product's deletion behavior.

If the backend no longer recognizes a cloud thread, Codex Desktop should reconcile or remove the stale Recents entry rather than repeatedly showing an action that always fails.

Additional information

Observed on 2026-08-27.

Related reports:

• #40432 — almost identical "stuck in Recents + archive failure + absent from web" symptom, but for CLI-created threads on macOS
• #30401 — "failed to archive" on PC
• #35125 — stale/orphaned conversations resurfacing in Tasks/Recents

No conversation content or workspace files appear to have been deleted. Exact thread titles, account identifiers, local paths, and raw logs are intentionally omitted.