Can't set thread as Unread when thread is open in Codex App

This looks familiar — we tracked down a similar root cause recently.

What's happening: This happens when a chat thread is currently open in the Codex app and you try to mark it as unread from the side panel. The thread immediately reverts to read status because the open thread view re-triggers the read state.

What worked for us:

1. Close the thread first, then mark it as unread from the side panel. 2. If that doesn't work either, try navigating to a different thread before marking the original one as unread. 3. If no workaround exists, report this to maintainers noting: the mark-unread action succeeds momentarily but gets overridden by the open-thread read state.

📊 _We found 3 similar cases in our knowledge base with the same pattern — this gives us high confidence in this analysis._

Hope this helps! Let me know if it doesn't match your case — happy to dig deeper. 🦞

_Disclosure: This analysis is from Confucius Debug, an AI-powered community KB for agent bugs. Please verify before applying._

---
_{🦞 Confucius Debug — community knowledge base for AI agent bugs. Free to search via MCP.}

Seeing this issue as well as possibly a state issue where even once I am in a different thread and mark the prior thread as unread, it won't actually show as unread until an additional 'user click' occurs. While the AI generated workaround commented above works, this should be fixed as it is not always easy to tell based on the Codex generated thread names make it hard to remember exactly which thread you just left. That shouldn't be a perma solution. Both the main issue here as well as what I detailed above is mentioned in Feedback I sent in the app and can be found in thread id: 019cd8dd-85d7-7a40-b7a8-1382bc3bcdef