Desktop chat thread reordering bug after compression
Cluster 68979. Data as of
Nothing open on GitHub. Fix merged in #69682 on 22 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #69682. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #69682. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a renderer-side bug where recent user messages are incorrectly re-stacked at the bottom of long threads following context compression, caused by broken ordinal matching during optimistic row preservation. The group covers the problem report and two related fixes scoping optimistic tail behavior.
Open issues0
Open PRs0
Fixes on record
-
#69649 fix(desktop): avoid duplicate inflight user rows on resume
files:
apps/desktop/e2e/fixtures.ts,apps/desktop/e2e/large-session-resume.spec.ts,apps/desktop/e2e/mock-server.ts,apps/desktop/e2e/scripts/seed_large_session.py,apps/desktop/src/app/session/hooks/use-session-actions/index.ts,apps/desktop/src/app/session/hooks/use-session-actions/utils.test.ts,apps/desktop/src/app/session/hooks/use-session-actions/utils.ts -
#69682 fix(desktop): prevent stale optimistic tails after compression
files:
apps/desktop/src/app/session/hooks/use-session-actions/utils.test.ts,apps/desktop/src/app/session/hooks/use-session-actions/utils.ts
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#68985 fix(desktop): bound optimistic user-row preservation to the in-flight tail (#68979) · superseded by another PR →
#69682,#68985,#69649
Closed issues · 1
- Closed#68979Desktop: long-thread reconciliation re-stacks recent user messages at thread bottom after context compression (ordinal matching breaks; renderer-only, DB is correct)
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.00means 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