[Desktop] Sort a project's Recents list by last message (the displayed timestamp column)
Summary
Inside a project, the Chats and tasks → Recents list is ordered by when each chat was created, but the right-hand column displays the last activity time. The result is that the visible timestamps are out of order, and there is no way to sort by the column that is actually shown.
Please make the Recents list sortable by last message / last activity (ideally the default), or make the far-right timestamp column clickable to sort.
Current behavior
Recents ordering ignores the displayed timestamp. Any chat that was created a while ago and then resumed keeps its original slot, so it appears far down the list even though it was just active.
Anonymized example from one project's Recents, in the exact order displayed:
| Position | Chat | Timestamp shown |
|---|---|---|
| 1 | Chat A | 49 minutes ago |
| 2 | Chat B | 3 hours ago |
| 3 | Chat C | 2 days ago |
| 4 | Chat D | 3 hours ago |
| 5 | Chat E | 5 days ago |
| 6-11 | ... | 5-6 days ago |
| 12 | Chat L | Aug 25 |
| 13 | Chat M | Yesterday |
| 14 | Chat N | 2 minutes ago |
| 15 | Chat O | Aug 19 |
Chat D (3 hours ago) sits below a chat last touched 2 days ago, and Chat M (yesterday) is buried between two chats from Aug 25. Every out-of-order row is an older chat that was resumed recently, which is consistent with the list sorting on creation time while rendering last-activity time.
Expected behavior
Recents should sort by last message / last activity, descending, matching the timestamp column that is displayed. Failing that, expose a sort control or make the timestamp column header sortable.
Why it matters
For a project with 15+ chats, this list is the primary way to get back to work in progress. Pinning is the only current workaround and it does not scale past a handful of chats. Every comparable list (email, Slack, iMessage, browser history) orders by last activity.
Environment
- Claude Desktop, project view (Cowork), Chats and tasks tab
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗