I often work in a single Codex thread for several hours, with many revisions and replacements of similar material.
In long threads, finding a specific earlier result becomes surprisingly difficult. I may remember roughly when a decision or change was made, but the UI gives me no reliable timestamp to locate it. Codex shows occasional date/time separators and a duration such as “Worked for 58s,” but many separate runs can appear inside one large untimestamped block.
As a result, I repeatedly have to scroll up and down through the thread, reread similar-looking responses, and manually search for the exact iteration I need. This takes a significant amount of time, interrupts the working flow, and becomes increasingly frustrating as the thread grows.
It is especially difficult when I need to reconstruct earlier context or compare several versions of the same text or implementation. The existing periodic timestamps are too sparse to serve as useful navigation landmarks.
Could every completed run show its actual completion time next to the duration?
Current:
Worked for 58s
Proposed:
Worked for 58s · Completed at 18:21
I would keep the duration because it is useful, but add the absolute completion time next to it. A compact timestamp, hover tooltip, or optional display setting would all work. Ideally, the full date, time, and time zone would also be accessible.
This is not just a cosmetic improvement. Per-run timestamps would provide stable landmarks inside long threads, reduce the time spent searching and scrolling, and make multi-hour Codex workflows much easier to navigate.
