fix: only break loop when respond_to_user is sole tool call

Previously the loop broke after respond_to_user even when other tools
ran in the same batch. If the model planned to emit follow-up tool
calls (e.g. finish_target) in a subsequent round-trip, those were
silently skipped. Now the loop only terminates when respond_to_user
was the only tool call — batched tool calls get their follow-up
round-trip as intended.

Author: SweetSophia

apps/webuiapps/src/components/ChatPanel/useConversationEngine.ts

@@ -160,7 +160,9 @@ export function useConversationEngine(deps: ConversationEngineDeps) {
       currentMessages = [...currentMessages, assistantMsg];
 
       // Execute each tool call
-      let stopLoop = false;
+      const hasRespondToUser = response.toolCalls.some(
+        (tc) => tc.function.name === 'respond_to_user',
+      );
       for (const tc of response.toolCalls) {
         const result = await executeToolCall(tc, {
           mm,
@@ -172,17 +174,15 @@ export function useConversationEngine(deps: ConversationEngineDeps) {
           callbacks: callbacksRef.current,
         });
         currentMessages = [...currentMessages, result];
-        // Mark respond_to_user as terminal — still execute remaining tool calls
-        // (e.g. finish_target) but skip the next model round-trip afterward
-        if (tc.function.name === 'respond_to_user') {
-          stopLoop = true;
-        }
       }
 
       // Update chat history (skip system message)
       callbacksRef.current.setChatHistory(currentMessages.slice(1));
 
-      if (stopLoop) break;
+      // Only break when respond_to_user was the sole tool call — if other
+      // tools ran in the same batch the model may still need a follow-up
+      // round-trip (e.g. finish_target) to commit state updates.
+      if (hasRespondToUser && response.toolCalls.length === 1) break;
     }
   }, []);