Fix approval flow for queued messages in Task.ts

When messages are queued while a tool is waiting for approval, they now properly handle the approval before sending. This prevents tools from being rejected when processing queued messages.

- Modified Task.ts to check if the ask type requires approval (tool, command, browser_action_launch, use_mcp_server)
- For approval-required asks, use handleWebviewAskResponse('yesButtonClicked') instead of setMessageResponse()
- For other ask types like followup, continue using setMessageResponse() as before

This ensures the correct order: approve tools first, then send messages.

Author: daniel-lxs

src/core/task/Task.ts

@@ -845,8 +845,19 @@ export class Task extends EventEmitter<TaskEvents> implements TaskLike {
 			const message = this.messageQueueService.dequeueMessage()
 
 			if (message) {
-				// Fulfill the ask directly to avoid re-queuing via the webview while sending is disabled
-				this.setMessageResponse(message.text, message.images)
+				// Check if this is a tool approval ask that needs to be handled
+				if (
+					type === "tool" ||
+					type === "command" ||
+					type === "browser_action_launch" ||
+					type === "use_mcp_server"
+				) {
+					// For tool approvals, we need to approve first, then send the message if there's text/images
+					this.handleWebviewAskResponse("yesButtonClicked", message.text, message.images)
+				} else {
+					// For other ask types (like followup), fulfill the ask directly
+					this.setMessageResponse(message.text, message.images)
+				}
 			}
 		}