[Bug]: Minimap "Next turn" button stops moving partway down a long thread#33026

opened3d agobyTtenyoru

Before submitting

I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

Open a long thread where one user message is followed directly by another (for example, a follow-up sent before the agent replied).
Hover over the left edge of the chat to show the minimap.
Starting above those messages, click the minimap's down button ("Next turn") repeatedly.

Expected behavior

Each click moves to the next turn, until the last turn.

Actual behavior

The first few clicks work. When the view reaches the adjacent user messages, it stops moving. The same four ticks stay highlighted and further clicks do nothing, even though many turns remain below. In the attached clip, clicks move the view until about 0:03, then do nothing for the last ~5 s.

Likely cause (from reading the code, not yet confirmed): onSelect in MessagesTimeline.tsx scrolls to the target row with viewOffset: 24, which leaves the bottom of the row above inside the visible range. resolveTimelineMinimapCurrentIndex treats the first user message in the visible range as the current turn. When the row above the target is also a user message, the current turn resolves back to it, so "Next turn" targets the same row on every click.

Impact

Minor bug or occasional failure

Version or commit

Desktop 0.1.7 (AppImage). The minimap code involved is unchanged on main @ 6577c6b61.