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

Version 26.305.950 (863)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.2.0 arm64 arm

What issue are you seeing?

Codex desktop is showing stale/orphaned thread entries that cannot be reopened or archived. For thread IDs 019ccff2-7936-74e2-b59d-f678c2860b10 and 019ccf94-8e1d-72b2-a061-72bc1db23b15, the UI still surfaces them, but the local thread store has no matching rollout/thread record. For 019ccff2-7936-74e2-b59d-f678c2860b10, the app log shows thread/resume failing with no rollout found for thread id ....

Submitted feedback with: 019cd5bf-c102-7612-9f3a-2ea899da81f8

What steps can reproduce the bug?

Repro is not fully deterministic yet, but the broken state is reproducible once a stale/orphaned thread entry exists in the desktop UI.

Observed repro path:

1. Open Codex desktop and navigate to a thread entry that is still shown in the sidebar/list.
2. Click the thread to reopen it.
3. Codex attempts thread/resume, but the backing rollout/thread metadata is missing locally.
4. The thread cannot be opened, and it also cannot be archived/cleaned up from the UI.

Observed error:
no rollout found for thread id <thread_id>

What is the expected behavior?

If a thread no longer has backing metadata, Codex should either hide it automatically or provide a working cleanup/remove/archive path instead of leaving a broken UI entry.

Additional information

No response