[Windows] Per-thread last activity timestamps disappeared from the Codex sidebar
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT/Codex Desktop 26.715.3651 (Windows x64)
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows 10, 64-bit, x64
What issue are you seeing?
After updating to the latest integrated ChatGPT/Codex Desktop app, the Codex sidebar no longer displays the relative last-activity time for individual threads.
Previous versions displayed useful timestamps such as 5m, 2h, or 3d next to each thread. In the current version, the sidebar only displays the thread title and its host or status indicator.
This makes it difficult to manage a large number of threads because I can no longer determine at a glance which thread was used recently and which thread has been inactive for a long time.
The timestamp data does not appear to be missing from the backend. The public Codex app-server API still exposes recencyAt and supports the recency_at sorting key, so this appears to be a regression in the Desktop sidebar UI.
What steps can reproduce the bug?
- Open the latest ChatGPT/Codex Desktop app on Windows 10.
- Open the Codex sidebar containing multiple threads with different last-activity times.
- Inspect the information displayed for each thread.
- Observe that the relative last-activity timestamp is no longer displayed.
- Only the thread title and host or status information remain visible.
What is the expected behavior?
Each thread in the Codex sidebar should display its relative last-activity time, as previous versions did.
Examples:
5m2h3d
The displayed value should preferably use recencyAt and refresh when a new turn starts.
If the timestamp was intentionally removed because of limited sidebar space, please provide a setting such as:
Show last activity time in sidebar
The setting should be enabled by default for existing users.
Additional information
This behavior appears to be a regression from the previously released Codex Desktop interface.
The last-activity timestamp is important when managing many concurrent or pinned threads. It is not merely decorative information; it is a primary navigation signal that helps users quickly locate recent work.
The same behavior has also been reported on macOS in issue #32172, so the regression appears to affect more than one desktop platform.
I can provide screenshots showing the previous and current sidebar behavior if needed.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗