Codex user highlights difficulty tracking outputs across many sessions
A Reddit user says managing multiple Codex app sessions becomes difficult because repeated task titles make sessions hard to distinguish and useful answers may exist only in old conversations. The user also reports that unread indicators disappear without confirming that the underlying work was reviewed, and asks others how they track unfinished sessions, decisions and outputs.
The post provides a user-level signal about a usability gap in multi-session Codex workflows, particularly when outputs are spread across conversations, files and code changes.
Lately I am using codex app alottt but with more created sessions it gets veryyy hard for me to keep track of what happened where.
The titles are often just sameeee because a lot of my tasks are related to the one project. But when the list gets longer then things kinda start getting very blurred. And at times I have to open soooo many sessions to find the one I am looking for. And that affects output as well. Like some sessions change the codebase directly. And I see some are creating markdown files. And then some have some useful answer that only exists in the conversation. And then a few days later, I do remember that Codex solved something, but I cannot remember at alll like whether the result was in a file or branch or an old chat.
The blue unread dots only help when I open a session. So at times I quickly skim a result and then I plan to come back later but later I forget it. Also the unread dot disappears even though I have not reviewed the work or done anything with it. And then I cant even search it because I do not remember the exact session title or wording or anything.