Skip to content

fix(web): follow the coordinator's reply to its end after the person sends #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brianjfox merged 1 commit into from
Nov 2, 2026
Merged

fix(web): follow the coordinator's reply to its end after the person sends #108

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion apps/web/src/pages/workspace/transcript.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down Expand Up @@ -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}
Expand Down