From 35412fd3efca47aa79daae457f953b2aebbd3a75 Mon Sep 17 00:00:00 2001 From: nesquena-hermes Date: Mon, 22 Jun 2026 21:27:57 +0000 Subject: [PATCH] =?UTF-8?q?Release=20v0.51.591=20=E2=80=94=20Release=20UX?= =?UTF-8?q?=20(stop=20transcript=20jumping=20to=20first=20message,=20#4721?= =?UTF-8?q?/#4720)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8d2d05df..0feebddb 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,8 @@ ## [Unreleased] +## [v0.51.591] — 2026-06-22 — Release UX (stop transcript jumping to first message on completion) + ### Fixed - **The transcript no longer jumps to the first message after every completion.** On a long conversation that loaded truncated, finishing a turn snapped the viewport to the top. The `done` event replaced the transcript with the full payload and expanded the render window to all messages, but left `_oldestIdx` stale — so the absolute scroll anchor (introduced with the read-position work) resolved to the wrong row and the view jumped to the start. The completion handler now resets `_oldestIdx` from the payload exactly like the other full-load paths, keeping the reader anchored where they were. Pinned-at-bottom readers still follow to the latest message. (#4720)