Desktop app: unarchiving an old thread reorders it to the top of the thread list

[twentyOne2x]

Summary

In the Codex macOS desktop app, unarchiving an old thread can make it appear at the top of the thread list as if it were recently active, even though the conversation itself is old.

Problem

After unarchiving, the thread appears to be sorted by a recent internal/tool timestamp rather than by the thread's real chronological position. This makes an old thread look new and disrupts list ordering inside the repo/project.

Observed behavior

• Archive an older thread
• Unarchive it later
• The thread jumps to the top / near the top of the list
• It appears to be ordered by a recent tool/unarchive-related timestamp instead of the thread's actual conversation recency

Expected behavior

Unarchiving should restore the thread without making it look newly active unless there was actual new conversation activity. Sorting should remain stable and reflect the correct thread time semantics.

Platform

macOS desktop app

Related

Possibly related to archived-thread handling issues such as #12166, but this report is specifically about incorrect ordering after unarchive.

[GlyphFlipper]

IMO this isn't a definitive issue. Different users might have different preferences. Even a single user might have preferences that span multiple contexts. A sort option would probably be better [created, last updated, by name, manual, etc.].