NousResearch/hermes-agent

Desktop timeline turn ordering and placement bugs

Cluster 118002. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #119878 on 23 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #119878. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #119878. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #119878, then check it covers your case.

Read #119878 Pick up a Lab task

These items concern bugs where turns appear duplicated, misplaced, or pinned at incorrect positions in the desktop virtualized timeline, particularly after rehydration or transcript refresh in long sessions.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#119878 fix(desktop): stop duplicate and misplaced turns after transcript refresh

merged to main

files: apps/desktop/src/app/session/hooks/use-session-actions/utils.test.ts, apps/desktop/src/app/session/hooks/use-session-actions/utils.ts, apps/desktop/src/lib/chat-messages/reconciliation.test.ts, apps/desktop/src/lib/chat-messages/reconciliation.ts

2 PRs closed without merging

From the close comments: superseded by another PR 2

#118228 fix(desktop): stop mid-turn narration bubbles pinning below newer turns after rehydrate · superseded by another PR → #120809, #118228, #119362, #119511
#118719 fix(desktop): reseat a preserved failed turn instead of repainting it at the tail · superseded by another PR → #119878, #118002

Closed issues · 1

Closed#118002[Bug] Desktop: old message appears at the newest-message position (virtualized timeline ordering regression in long sessions)

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs: #119878
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/118002.json
cluster/118002.md