From 5d44f1631b37cc680b69265f436fa1defa2e594c Mon Sep 17 00:00:00 2001
From: hu <hu@pro-hacker-mac.local>
Date: Wed, 18 Feb 2026 11:13:57 +0800
Subject: [PATCH] fix: remove hardcoded disableBlockStreaming to honor agent
 config for TUI

The chat.send handler was hardcoding disableBlockStreaming: true, which
overrode the agents.defaults.blockStreamingDefault config setting. This
caused TUI to ignore the blockStreamingDefault config and always stream
token-by-token, overwriting previous content.

Now the blockStreamingDefault config is respected for TUI/webchat just
like other channels.

Fixes #19643
---
 src/gateway/server-methods/chat.ts | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/gateway/server-methods/chat.ts b/src/gateway/server-methods/chat.ts
index 6c0b90e9438..29d099d93f8 100644
--- a/src/gateway/server-methods/chat.ts
+++ b/src/gateway/server-methods/chat.ts
@@ -898,7 +898,6 @@ export const chatHandlers: GatewayRequestHandlers = {
           runId: clientRunId,
           abortSignal: abortController.signal,
           images: parsedImages.length > 0 ? parsedImages : undefined,
-          disableBlockStreaming: true,
           onAgentRunStart: (runId) => {
             agentRunStarted = true;
             const connId = typeof client?.connId === "string" ? client.connId : undefined;