Codex Desktop recents timestamp appears to use thread creation time instead of last active time

Summary

Codex Desktop appears to show a stale relative timestamp for an active/resumed thread. The visible recents/corner timestamp can read like the session was last run several days ago even while the thread is actively being used.

Observed behavior

• A Codex Desktop thread created several days earlier was resumed and actively used today.
• The local session storage for the thread was modified/accessed today.
• The UI still displayed a relative timestamp such as 3 days ago, which appears to match the thread creation age rather than last activity.

Expected behavior

The visible recents/corner timestamp should represent the thread's last active / last run time, not the original creation time.

If creation time is useful, it should be shown separately from activity time.

Possible fix

Use a last-activity field for the visible timestamp, for example:

displayAge = timeAgo(thread.lastActiveAt ?? thread.updatedAt ?? thread.createdAt)

Suggested UI wording:

• Created: <date>
• Last active: <relative time>

Why this matters

When a resumed thread is actively being used but still says something like 3 days ago, it makes the session look stale or inactive even though work is happening in it.