Repository navigation
fix: keep phone messages and chunked replies consistent - #200
Merged
Merged
Conversation
WSL043
added a commit
that referenced
this pull request
Oct 27, 2026
fix: keep phone messages and chunked replies consistent
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.
Phone submissions briefly appeared as two user bubbles because the start response repeated the optimistic message and committed history changed its item/turn identity. Return an empty start acknowledgement, link the server item to the client's submission ID, and retain the displayed identities through history restoration, including repeated identical prompts.
Also serialize each relay stream's outgoing messages and snapshot their content before asynchronous chunk delivery. Finish tool image reads before closing the turn, use the event's own message, and avoid completing a tool before its result exists. Normal info logs record bounded protocol metadata with hashed identifiers; request bodies and image bytes are excluded.
Validation: 777 behavior tests and 120 delivery tests passed after rebuilding the checked-in backend bundle. The user confirmed on iPhone that the duplicate user bubble no longer appears. Chunk order, snapshots, delayed image reads and history identity have protocol regression coverage; these checks do not establish successful iPhone image rendering.
Depends on #199 for the search-only fix and internal delivery version. This PR contains no sketch drawing changes, final-answer image promotion, virtual image filesystem, or experimental image helper. The separate iPhone final-answer image loading problem remains under investigation. No version publication is requested.