What happened
Creating a branch from an existing answer produces a new conversation whose sidebar row has no timestamp. In the conversation view, it sorts below older conversations until a new message is sent in the branch.
Expected: creating a branch is recent activity. The new branch should immediately show “just now” and appear ahead of older conversations within its pinned/unpinned section.
How to reproduce
- Open Desktop with existing conversations in the sidebar's conversation view.
- Open an older conversation and use the branch action below a completed assistant answer.
- Leave the new branch open without sending another message.
- Inspect its timestamp and position in the sidebar.
The new row has no timestamp and is placed after conversations that have a last-message timestamp.
Environment
- Maka source commit reproduced:
acaa29e40
- OS: macOS 15.7.3 (24G419)
- Surface: Desktop, conversation sidebar
- Node.js: v24.14.0
Logs, screenshots, or additional context
The Host already supplies activityAt for catalog rows, including newly created branches. SessionHistoryList displays and sorts by lastMessageAt instead. A branch can have no own message timestamp, so the row renders no time and the comparator treats its timestamp as zero.
Deterministic regression checks against the actual list renderer reproduced both symptoms: the time label was absent instead of “just now”, and the rendered order was [source, branch] instead of [branch, source]. A row with older copied-message metadata also displayed the old age despite a newer catalog activity timestamp.
Submitted with Codex on behalf of @liuxiaocs7.
What happened
Creating a branch from an existing answer produces a new conversation whose sidebar row has no timestamp. In the conversation view, it sorts below older conversations until a new message is sent in the branch.
Expected: creating a branch is recent activity. The new branch should immediately show “just now” and appear ahead of older conversations within its pinned/unpinned section.
How to reproduce
The new row has no timestamp and is placed after conversations that have a last-message timestamp.
Environment
acaa29e40Logs, screenshots, or additional context
The Host already supplies
activityAtfor catalog rows, including newly created branches.SessionHistoryListdisplays and sorts bylastMessageAtinstead. A branch can have no own message timestamp, so the row renders no time and the comparator treats its timestamp as zero.Deterministic regression checks against the actual list renderer reproduced both symptoms: the time label was absent instead of “just now”, and the rendered order was
[source, branch]instead of[branch, source]. A row with older copied-message metadata also displayed the old age despite a newer catalog activity timestamp.Submitted with Codex on behalf of @liuxiaocs7.