perf(site/src): optimistically edit chat messages#23976
Draft
ethanndickson wants to merge 1 commit intomainfrom
Draft
perf(site/src): optimistically edit chat messages#23976ethanndickson wants to merge 1 commit intomainfrom
ethanndickson wants to merge 1 commit intomainfrom
Conversation
67c57ea to
c82ceb4
Compare
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
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.
Previously, editing a past user message in Agents chat waited for the PATCH round-trip and follow-up refetch before the transcript tail visibly changed. Even after the initial optimistic update, the edited bubble could still flicker away while the UI reconciled from the old user-message ID to the new server-assigned replacement ID.
Keep message editing optimistic end-to-end: update the edited user bubble and truncate the tail immediately, carry that state through the authoritative replacement message until the cache catches up, and roll back the visible draft cleanly on failure. This also centralizes edited-submission request/render preparation and adds focused regression coverage around the chat store bridge, rollback behavior, and attachment/draft restoration.