pastilhasandClaude Opus 5
0210e85762
Regression from the fold change. Scroll-up paging is driven by a scroll listener, and a scroll listener only fires on a list that actually scrolls. That was always true and never mattered, because the turn you were looking at rendered in full and was tall enough on its own. Folding on reload broke it. A window of twenty messages can be one turn with eighteen tool calls, which collapses to three short rows: no overflow, no scroll event, and paging never starts. The whole transcript above becomes unreachable — which reads as lost history rather than as a fetch that never fired. So don't wait for a scroll that cannot happen: after each render, if there is more to load and the content does not overflow its viewport, load the next page. Terminates because each pass either fills the viewport or exhausts the transcript. This also fixes a latent case that predates folding — any first window short enough to fit on screen could never be paged past. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>