Skip to content

perf(cli): render one smaller page of transcript messages #1550

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
obadakhalili merged 1 commit into from
Oct 23, 2026
Merged

perf(cli): render one smaller page of transcript messages #1550

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
17 changes: 15 additions & 2 deletions cli/src/hooks/use-chat-messages.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,21 @@ import { buildMessageTree } from '../utils/message-tree-utils'

import type { ChatMessage, ContentBlock } from '../types/chat'

/** Batch size for message pagination */
const MESSAGE_BATCH_SIZE = 15
/**
* Batch size for message pagination.
*
* This is a frame-cost knob, not a layout preference. A re-render lays out
* every rendered node, and the cost is linear in that count whether or not the
* node changed — an unchanged 1,500-node transcript measures ~60 ms per frame
* against ~0.1 ms when nothing re-renders, so memoizing cannot rescue it. A
* streamed chunk re-renders the whole page, which is why a long conversation
* used to fall behind its own output.
*
* One page at 15 messages measured ~11.5k nodes and ~60 ms per frame; six
* costs roughly a third of that. `LoadPreviousButton` already offers the rest,
* so the trade is one click of history for frames that keep up with the stream.
*/
const MESSAGE_BATCH_SIZE = 6

/**
* Options for useChatMessages hook.
Expand Down
Loading