Repository navigation
perf: update chats incrementally instead of replaying their history - #650
Open
rschmukler wants to merge 1 commit into
Open
rschmukler wants to merge 1 commit into
rschmukler wants to merge 1 commit into
Conversation
rschmukler
marked this pull request as ready for review
October 15, 2026 18:45
rschmukler
force-pushed
the
rs/incremental-chat-updates
branch
2 times, most recently
from
October 15, 2026 19:12
c6545d2 to
33aacfa
Compare
Add the incrementalUpdates client capability. For clients declaring it: - chat/rollback emits chat/truncated instead of chat/cleared plus a replay of the kept messages. - chat/addFlag emits only the new flag, positioned by afterContentId. - Chats the server creates (chat/fork, /fork, /btw) stream only their newest historyPageSize messages (default 50), with the paging meta in the new history field of chat/opened so older ones load via chat/history. Other clients keep the full replay behavior.
rschmukler
force-pushed
the
rs/incremental-chat-updates
branch
from
October 15, 2026 19:34
33aacfa to
aaa2e68
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the incrementalUpdates client capability. For clients declaring it:
chat/rollback emits chat/truncated instead of chat/cleared plus a replay of the kept messages.
chat/addFlag emits only the new flag, positioned by afterContentId.
Chats the server creates (chat/fork, /fork, /btw) stream only their newest historyPageSize messages (default 50), with the paging meta in the new history field of chat/opened so older ones load via chat/history. Other clients keep the full replay behavior.
I added a entry in changelog under unreleased section.
This is not an AI slop. (Please take a human time to write a comprehensive context about the problem, alternatives and rationale)