-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Description
Summary
The resume picker list is ordered by created_at, but the UI column is labeled “Updated,” so the timestamps appear out of order.
Steps to reproduce
- Run
codex resume - Observe the “Updated” column ordering (e.g., a newer “1 minute ago” entry can appear below “1 hour ago”)
Expected
Rows should be ordered by the displayed “Updated” timestamp (most recent first).
Actual
Rows are ordered by created_at while the “Updated” column shows a different timestamp.
Evidence
- Before: (attach Image update summary to auto #1)
- After: (attach Image (cleanup) add link to https://cookbook.openai.com for apply_patch and minor tidy up #2)
Proposed fix
In the resume picker, request ThreadSortKey::UpdatedAt instead of CreatedAt so ordering matches the “Updated” column.
Code change (suggested)
- ThreadSortKey::CreatedAt
+ ThreadSortKey::UpdatedAt
File: codex-rs/tui/src/resume_picker.rs (also update the resume picker snapshot test call in the same file to match)
Notes
Using UpdatedAt relies on file mtime sorting; this may be a bit heavier than CreatedAt, but it aligns with the UI label.
Local validation
cargo build -p codex-clicargo test -p codex-tui
Also, a side note: it would be nice if you could make the repository more friendly for submitting an issue via the codex because I wasn't able to neatly fit this into a bug report and I don't really want to copy and paste all the text in.
