I’m seeing a reproducible task-discovery synchronization issue in the Codex desktop app on Windows.
Steps to reproduce
From an existing local Codex task, create another task in the same saved Git project using an isolated worktree.
Task creation returns a temporary clientThreadId while worktree setup is in progress.
The new task is created successfully and completes its first turn.
Query the active task list repeatedly from the originating task.
Expected
After setup completes, the new task should appear in the task list with its resolved threadId, so the originating task can discover, read, or wait for it.
Actual
The task did not appear in either the active or archived task listings, even about 15 minutes after it completed. No unavailable host was reported. The task was visible in the Codex desktop UI and had a valid codex://threads/... deep link. When the resolved threadId from that link was supplied manually, direct retrieval succeeded immediately and returned the completed turn.
This suggests task execution and storage were healthy, while either the clientThreadId-to-threadId resolution or the task-list index was not propagated to the originating task.
Environment
Codex desktop app on Windows
Local host
Saved Git project
New task created in an isolated worktree
Workaround
Copy the new task’s codex:// deep link from the UI and provide its resolved threadId to the originating task for direct retrieval.
I can provide the full temporary ID, resolved task ID, source task ID, and timestamps privately if useful.
You are welcome to discuss Codex issues here. However, the official place to report and track Codex bugs is the OpenAI Codex GitHub issue tracker.
I asked ChatGPT to search for the closest related issue, and it identified:
If that issue describes the same problem you are experiencing, consider adding a reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.
If it does not match your problem closely enough, search the existing Codex issues for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.
Looks like the task itself is completing fine, but the task-list index isn’t getting updated. The fact that the resolved threadId works immediately through the deep link seems like a strong clue.
Thank you for the welcome and for pointing me to the official Codex issue tracker and #26861.
I reviewed #26861. It appears related, but my case may be a later-stage variant: the worktree was created successfully, the task completed, and the resolved threadId could be read directly. However, the task still never appeared in either the active or archived task listings.
I also found #30385, which seems closer because it describes completed Windows tasks that can be loaded directly by threadId but are missing from list_threads and the normal task discovery paths.
I’ll compare the existing issues carefully before opening a duplicate. Thanks again for the helpful direction.
reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.