fix(chat): concatenate all text parts in conversation item rendering#901
Merged
harshithmullapudi merged 1 commit intoJun 11, 2026
Merged
Conversation
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.
Problem
message.parts.find(p => p.type === "text")returns the first text chunk, which is empty in multi-step agent turns. After a tool call, the AI SDK produces astep-start+ emptytextpart for the tool-use step, followed by anotherstep-start+ the real response text..find()grabs the empty one → editor gets""→ blank message.Solution
Replace
.find()with.filter()+.map().join()to concatenate all non-empty text parts into a single string for the TipTap editor.Changes
apps/webapp/app/components/conversation/conversation-item.client.tsx.find()with.filter()to collect all non-empty text partsuseEditorinitial content anduseEffectto use the combined stringSDK_Text_Fix.mov
Fix #900