Archived automation runs remain unread in Previous runs, but are not discoverable as threads or inbox items

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

26.311.21342

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

After two automation runs auto-archived, they still appeared as unread red-dot entries under Previous runs. I could not find matching unread threads in the normal thread list, and Inbox was empty. This made it look like there were unread runs somewhere in the app that were not actually navigable from the main UI.

From local state inspection, both runs were archived but still unread:

• automation_runs.status = ARCHIVED
• automation_runs.read_at = NULL
• threads.archived = 1

The automation's final output explicitly included an inbox item followed by ::archive-thread, so the archive itself looks intentional. The likely bug is that archived automation runs can still be surfaced as unread without a corresponding entry in the thread list or Inbox.

What steps can reproduce the bug?

1. Run an automation that posts an inbox item and then archives its thread.
2. Let it finish with no repository changes and no follow-up action required.
3. Open the automation details and check Previous runs.
4. Observe a red unread indicator on the archived run.
5. Try to find the same unread run in the normal thread list or Inbox.

In my case, the affected run thread IDs were:

• 019ce9ab-7c52-7202-bb2f-be333a6be83a
• 019ce9af-7fec-7451-9ad0-65c87a950f54

What is the expected behavior?

If an automation run is archived and no longer shown as a normal thread, it should either stop showing as unread or provide a direct way to open and mark that archived run as read. The unread state should be consistent across automation history, thread list, and Inbox.

Additional information

• Observed on March 14, 2026 (Asia/Seoul).
• Stored runtime metadata for the affected runs showed 0.115.0-alpha.11.
• Both affected runs were "no changes needed" automation completions, so this seems unrelated to repository edits and more like a UI/state consistency issue.
• I can attach a screenshot showing the unread indicators in Previous runs.

<img width="735" height="499" alt="Image" src="https://github.com/user-attachments/assets/8a126b12-93bb-4702-9548-952d311940b9" />