github/AutoGPT
1
1
Fork 0
mirror of https://github.com/Significant-Gravitas/AutoGPT.git synced 2026-04-30 03:00:41 -04:00
Code Issues Packages Projects Releases Wiki Activity

fix(frontend): memoize DefaultChatTransport to prevent mid-stream resets

Browse Source 
Wraps the DefaultChatTransport instantiation in useMemo([sessionId]) so
the same transport object is reused across renders. Without memoisation,
each streaming chunk (which triggers a re-render) created a new transport
instance, resetting useChat's internal Chat state mid-stream. Matches the
pattern already used in useCopilotStream.ts.
This commit is contained in:
majdyz
2026-04-11 09:25:37 +07:00
parent e79214f3dd
commit 1935137c10
1 changed files with 36 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

69
autogpt_platform/frontend/src/app/(platform)/build/components/BuilderChatPanel/useBuilderChatPanel.ts
View File

@@ -8,6 +8,7 @@ import {
type KeyboardEvent,
type RefObject,
useEffect,
useMemo,
useRef,
useState,
} from "react";
@@ -244,32 +245,42 @@ export function useBuilderChatPanel({
// eslint-disable-next-line react-hooks/exhaustive-deps
}, [isOpen, sessionId, sessionError]);
// Transport is recreated when sessionId changes (at most once per graph navigation),
// so memoisation provides no meaningful benefit — use a plain conditional.
const transport = sessionId
? new DefaultChatTransport({
api: `${environment.getAGPTServerBaseUrl()}/api/chat/sessions/${sessionId}/stream`,
prepareSendMessagesRequest: async ({ messages }) => {
const last = messages.at(-1);
if (!last)
throw new Error("No message to send — messages array is empty.");
const { token, error } = await getWebSocketToken();
if (error || !token)
throw new Error("Authentication failed — please sign in again.");
const messageText = extractTextFromParts(last.parts ?? []);
return {
body: {
message: messageText,
is_user_message: last.role === "user",
context: null,
file_ids: null,
mode: null,
// Memoised so the same DefaultChatTransport instance is reused across
// re-renders (e.g. every streaming chunk triggers a render). Recreating it
// on each render resets useChat's internal Chat instance mid-stream, causing
// the streaming connection to break. Only recreate when sessionId changes.
const transport = useMemo(
() =>
sessionId
? new DefaultChatTransport({
api: `${environment.getAGPTServerBaseUrl()}/api/chat/sessions/${sessionId}/stream`,
prepareSendMessagesRequest: async ({ messages }) => {
const last = messages.at(-1);
if (!last)
throw new Error(
"No message to send — messages array is empty.",
);
const { token, error } = await getWebSocketToken();
if (error || !token)
throw new Error(
"Authentication failed — please sign in again.",
);
const messageText = extractTextFromParts(last.parts ?? []);
return {
body: {
message: messageText,
is_user_message: last.role === "user",
context: null,
file_ids: null,
mode: null,
},
headers: { Authorization: `Bearer ${token}` },
};
},
headers: { Authorization: `Bearer ${token}` },
};
},
})
: null;
})
: null,
[sessionId],
);
const { messages, setMessages, sendMessage, stop, status, error } = useChat({
id: sessionId ?? undefined,
@@ -315,14 +326,6 @@ export function useBuilderChatPanel({
// new messages, losing actions.
useEffect(() => {
if (status !== "ready") return;
// Guard against a navigation race: when flowID changes, the
// flow-reset effect clears `messages` + `parsedActions` but those
// state updates aren't committed until the next render. If this
// effect ran on a render where the ref still holds the *previous*
// flowID, we'd briefly re-populate parsedActions from the old
// graph's stale messages, causing old action buttons to flash in
// the new chat panel. Skip parsing until the ref catches up.
if (currentFlowIDRef.current !== flowID) return;
const cache = parsedActionsCacheRef.current;
const startIndex = lastParsedMessageIndexRef.current + 1;
let appendedAny = false;