Codex Desktop 26.810.7004.0 shows subagent child threads as top-level sidebar conversations after update

Summary

I am also experiencing a serious sidebar/history regression on Codex Desktop for Windows after a recent update. The Recent list is now filled with duplicated task titles and many Untitled session entries that appear to be subagent child threads shown as normal top-level conversations.

Environment

• Codex Desktop: 26.810.7004.0
• Platform: Windows
• Account: ChatGPT Pro
• The problem started after a recent Codex Desktop update.

Observed behavior

• Subagent child threads appear as independent entries in the main Recent list.
• Multiple entries can have the same or nearly identical task titles.
• The list is increasingly dominated by automated child tasks instead of user-created conversations.
• It is difficult to identify and reopen the actual parent task or the conversation I was working on.

Local diagnostics and suspected root cause

The underlying conversation data is still present and the local databases pass integrity checks, so this does not appear to be data loss. Local inspection shows that the sidebar/indexing layer is incorrectly treating subagent threads as visible top-level conversations:

• The core state database contains threads whose source is marked as subagent.
• The visible local thread catalog includes 210 active subagent threads.
• The catalog contains 338 visible entries in total.
• This suggests that the recent-conversation synchronization or session-classification logic is no longer filtering subagent child threads out of the top-level sidebar, or is failing to recognize their subagent metadata during the catalog rebuild.

The exact commit that introduced the regression is not yet known, but the behavior appears to be caused by an update-related regression in the sidebar/index synchronization path rather than by corrupted or deleted conversation data.

Impact

This has a significant impact on daily work. The Recent list is no longer a reliable way to find active tasks or resume previous work. I spend time searching through duplicate and irrelevant child-thread entries, real parent conversations become difficult to locate, and it is easy to open the wrong session. For multi-step work, this breaks conversation continuity and makes the desktop app substantially harder to use.

Expected behavior

Subagent child threads should either:

• be hidden from the main Recent list by default;
• be grouped under their parent task; or
• be clearly marked and excluded from the top-level recent-conversation limit.

This appears related to #34090 and #25341.

Reproduce the regression on Windows with Codex Desktop 26.810.7004.0, then trace the sidebar/index synchronization and session-classification path described in the report. Done means subagent child threads no longer appear as independent top-level Recent entries, or are consistently grouped or clearly excluded from the top-level list.