Codex app: per-thread inbox of unread turn results for queued tasks

What variant of Codex are you using?

Codex desktop app on macOS

What feature would you like to see?

Problem

I often queue several tasks in the same Codex conversation and return after they have finished. I naturally read the latest result, but earlier task results can be buried above it. I cannot reliably tell which individual results I have already reviewed.

A thread-level unread dot does not tell me which turns still need attention. A completion sound or desktop notification also does not provide a persistent checklist when several tasks finish while I am away.

Example workflow

1. Submit task A, then queue tasks B and C in the same conversation.
2. Let all three finish while working elsewhere.
3. Return and read C's final response.
4. Need to find A and B's results and know whether they still need review, without manually scanning the whole conversation.

Requested behavior

• A per-thread list and count of unread or unreviewed final turn results, with a short task label, completion time, and link to the exact result.
• A "Jump to first unread result" action, plus navigation to the next unread result.
• A per-result "Mark reviewed" action and an explicit "Mark all reviewed" action.
• Opening the conversation or viewing C must not implicitly mark A and B reviewed. The list should remain available across app restarts.
• Keep completed-but-unreviewed results separate from running tasks. Failed or interrupted turns should retain their actual status.

If the UI cannot reliably determine whether a result was read, an explicit "unreviewed" state is sufficient; simply focusing the window should not count as review.

Acceptance example

After A, B, and C finish, reviewing only C leaves A and B in the pending-review list. Selecting A jumps to A's final response. Marking A reviewed leaves only B. Restarting the app preserves B's pending-review state.

The scope is multiple turns inside one conversation, rather than only an inbox across separate conversations.

Additional information

Related but different: #27871 concerns read-state handling for automation-generated results; #3962 concerns completion sounds. This request is specifically about retaining and navigating individual turn results within one thread.

Original user feedback: https://x.com/jie_wang16261/status/2096293908217319524

No files or tests are named; start by locating the desktop app's per-thread turn-result state, navigation entry points, and persistence layer. Done means unread results remain distinct within one conversation, support jump and review actions, preserve status across restarts, and match the A/B/C acceptance example.