From 4ef796822c2c2b6a90204d9f524b5f0d4fbd7061 Mon Sep 17 00:00:00 2001
From: daniel-lxs <ricciodaniel98@gmail.com>
Date: Mon, 3 Nov 2025 10:55:21 -0500
Subject: [PATCH] fix: correct isStreaming logic when cost is defined

The logic was inverted - when cost is defined in api_req_started, it means the API request has finished (streaming is complete), so should return false, not true.
---
 webview-ui/src/components/chat/ChatView.tsx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/webview-ui/src/components/chat/ChatView.tsx b/webview-ui/src/components/chat/ChatView.tsx
index 42c93fa5b6..0aab84125c 100644
--- a/webview-ui/src/components/chat/ChatView.tsx
+++ b/webview-ui/src/components/chat/ChatView.tsx
@@ -558,7 +558,7 @@ const ChatViewComponent: React.ForwardRefRenderFunction<ChatViewRef, ChatViewPro
 
 					// Otherwise, check if cost is defined to determine if streaming is complete
 					if ("cost" in info && info.cost !== undefined) {
-						return true // API request has not finished yet.
+						return false // API request has finished.
 					}
 				}
 			}