fix: correct isStreaming logic when cost is defined

daniel-lxs · daniel-lxs · commit 4ef796822c2c · 2025-11-03T10:55:21.000-05:00
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.
diff --git 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.
 					}
 				}
 			}

Original file line number	Diff line number	Diff line change
`@@ -558,7 +558,7 @@ const ChatViewComponent: React.ForwardRefRenderFunction<ChatViewRef, ChatViewPro`
`558`	`558`
`559`	`559`	`// Otherwise, check if cost is defined to determine if streaming is complete`
`560`	`560`	`if ("cost" in info && info.cost !== undefined) {`
`561`		`- return true // API request has not finished yet.`
	`561`	`+ return false // API request has finished.`
`562`	`562`	`}`
`563`	`563`	`}`
`564`	`564`	`}`