Skip to content

Stabilized message.id during streamText call with multiple steps #6267

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
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
8 changes: 6 additions & 2 deletions packages/ui-utils/src/process-chat-response.ts
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ export async function processChatResponse({
parts: [],
};

let hasIdBeenEstablished = replaceLastMessage;
let currentTextPart: TextUIPart | undefined = undefined;
let currentReasoningPart: ReasoningUIPart | undefined = undefined;
let currentReasoningTextDetail:
Expand Down Expand Up @@ -364,9 +365,12 @@ export async function processChatResponse({
currentReasoningTextDetail = undefined;
},
onStartStepPart(value) {
// keep message id stable when we are updating an existing message:
if (!replaceLastMessage) {
// keep message id stable when we've already received a messageId
// need to stay consistent with behavior of appendResponseMessages
// in order for client and server to be in sync
if (!hasIdBeenEstablished) {
message.id = value.messageId;
hasIdBeenEstablished = true;
}

// add a step boundary part to the message
Expand Down