From eef9dff599230283329ba7783f247e58ba753f58 Mon Sep 17 00:00:00 2001
From: "Brian J. Fox" <bfox@brianjfox.com>
Date: Mon, 2 Nov 2026 18:49:56 +0000
Subject: [PATCH] fix(web): follow the coordinator's reply to its end after the
 person sends

---
 apps/web/src/pages/workspace/transcript.tsx | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/apps/web/src/pages/workspace/transcript.tsx b/apps/web/src/pages/workspace/transcript.tsx
index d724aab1..4fe9d97c 100644
--- a/apps/web/src/pages/workspace/transcript.tsx
+++ b/apps/web/src/pages/workspace/transcript.tsx
@@ -605,7 +605,7 @@ export function RoomThread({
   turns: readonly TranscriptTurn[];
   /** Specialist mail from their own threads, folded in between the turns. */
   updates?: readonly SpecialistUpdate[];
-  /** The reader's latest send, so the conversation settles on it. */
+  /** The reader's latest send, so the conversation follows the reply to it. */
   sentId?: string;
   /** The colleague is working on a reply. */
   thinking?: boolean;
@@ -864,7 +864,10 @@ export function RoomThread({
     },
   );
   return (
+    // The view follows the reply to its end once the person sends, and stays put when they scroll
+    // away, so a long answer is read without chasing it.
     <Conversation
+      scrollPolicy="stick"
       sentId={sentId}
       className="room-thread"
       data-mapped={mapTurns.length > 1 ? "" : undefined}