Task registration loss: create_thread returns a client ID that never resolves in list_threads
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From "About Codex" dialog)?
26.901.51231, Windows Desktop.
What subscription do you have?
Not applicable — observed via Desktop task APIs (create/list/wait/read thread).
What platform is your computer?
Windows 11 + WSL2 (Ubuntu 24.04). Agent environment: Windows-native.
What issue are you seeing?
Task registration loss: create_thread returns a client ID (client-new-thread:<id>), but the task never resolves — two subsequent authoritative list_threads checks found no task with the requested title and no usable server thread ID. No duplicate was created through the same path, so this is silent loss, not a race.
This is distinct from #16815 (creation fails with an AbsolutePathBuf error): here creation succeeds and registration is missing. No AbsolutePathBuf error text was observed anywhere in this flow.
What steps can reproduce the bug?
- In Codex Desktop on Windows, dispatch a task via
create_thread. - Record the returned
client-new-thread:<id>. - Run authoritative
list_threadschecks (we ran two). - Observe: no task with the requested title, no usable thread ID, and no duplicate.
What is the expected behavior?
The created task is visible to lookup (by title and by client ID), or creation fails loudly. Lookup should be idempotent: re-checking must never be the step that loses the task.
Additional information
Client ID available on request (truncated): client-new-thread:7c7c3a0d-…. Observed 2026-09-06 alongside empty-payload completions (see #28751), but as a separately reproduced failure — registration loss, not message loss.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the Desktop task API flow from create_thread through registration and list_threads, using the reported Windows 11 and WSL2 setup to reproduce it. Check the returned client-new-thread ID against authoritative list_threads results. Done means a created task is discoverable by title or client ID, or creation fails loudly without silently losing the registration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100