feat: enable multiple native tool calls per turn with failure guardrails (#9273)

packages/types/src/experiment.ts

@@ -12,6 +12,7 @@ export const experimentIds = [
 	"preventFocusDisruption",
 	"imageGeneration",
 	"runSlashCommand",
+	"multipleNativeToolCalls",
 ] as const
 
 export const experimentIdsSchema = z.enum(experimentIds)
@@ -28,6 +29,7 @@ export const experimentsSchema = z.object({
 	preventFocusDisruption: z.boolean().optional(),
 	imageGeneration: z.boolean().optional(),
 	runSlashCommand: z.boolean().optional(),
+	multipleNativeToolCalls: z.boolean().optional(),
 })
 
 export type Experiments = z.infer<typeof experimentsSchema>

src/api/providers/openrouter.ts

@@ -207,7 +207,6 @@ export class OpenRouterHandler extends BaseProvider implements SingleCompletionH
 						allow_fallbacks: false,
 					},
 				}),
-			parallel_tool_calls: false, // Ensure only one tool call at a time
 			...(transforms && { transforms }),
 			...(reasoning && { reasoning }),
 			...(metadata?.tools && { tools: metadata.tools }),

src/core/assistant-message/presentAssistantMessage.ts

@@ -71,8 +71,6 @@ export async function presentAssistantMessage(cline: Task) {
 	cline.presentAssistantMessageLocked = true
 	cline.presentAssistantMessageHasPendingUpdates = false
 
-	const cachedModelId = cline.api.getModel().id
-
 	if (cline.currentStreamingContentIndex >= cline.assistantMessageContent.length) {
 		// This may happen if the last content block was completed before
 		// streaming could finish. If streaming is finished, and we're out of
@@ -341,7 +339,8 @@ export async function presentAssistantMessage(cline: Task) {
 						return `[${block.name} for '${block.params.command}']`
 					case "read_file":
 						// Check if this model should use the simplified description
-						if (shouldUseSingleFileRead(cachedModelId)) {
+						const modelId = cline.api.getModel().id
+						if (shouldUseSingleFileRead(modelId)) {
 							return getSimpleReadFileToolDescription(block.name, block.params)
 						} else {
 							// Prefer native typed args when available; fall back to legacy params
@@ -476,6 +475,14 @@ export async function presentAssistantMessage(cline: Task) {
 			const toolCallId = (block as any).id
 			const toolProtocol = toolCallId ? TOOL_PROTOCOL.NATIVE : TOOL_PROTOCOL.XML
 
+			// Check experimental setting for multiple native tool calls
+			const provider = cline.providerRef.deref()
+			const state = await provider?.getState()
+			const isMultipleNativeToolCallsEnabled = experiments.isEnabled(
+				state?.experiments ?? {},
+				EXPERIMENT_IDS.MULTIPLE_NATIVE_TOOL_CALLS,
+			)
+
 			const pushToolResult = (content: ToolResponse) => {
 				if (toolProtocol === TOOL_PROTOCOL.NATIVE) {
 					// For native protocol, only allow ONE tool_result per tool call
@@ -531,10 +538,20 @@ export async function presentAssistantMessage(cline: Task) {
 					}
 				}
 
-				// Once a tool result has been collected, ignore all other tool
-				// uses since we should only ever present one tool result per
-				// message.
-				cline.didAlreadyUseTool = true
+				// For XML protocol: Only one tool per message is allowed
+				// For native protocol with experimental flag enabled: Multiple tools can be executed in sequence
+				// For native protocol with experimental flag disabled: Single tool per message (default safe behavior)
+				if (toolProtocol === TOOL_PROTOCOL.XML) {
+					// Once a tool result has been collected, ignore all other tool
+					// uses since we should only ever present one tool result per
+					// message (XML protocol only).
+					cline.didAlreadyUseTool = true
+				} else if (toolProtocol === TOOL_PROTOCOL.NATIVE && !isMultipleNativeToolCallsEnabled) {
+					// For native protocol with experimental flag disabled, enforce single tool per message
+					cline.didAlreadyUseTool = true
+				}
+				// If toolProtocol is NATIVE and isMultipleNativeToolCallsEnabled is true,
+				// allow multiple tool calls in sequence (don't set didAlreadyUseTool)
 			}
 
 			const askApproval = async (
@@ -791,7 +808,8 @@ export async function presentAssistantMessage(cline: Task) {
 					break
 				case "read_file":
 					// Check if this model should use the simplified single-file read tool
-					if (shouldUseSingleFileRead(cachedModelId)) {
+					const modelId = cline.api.getModel().id
+					if (shouldUseSingleFileRead(modelId)) {
 						await simpleReadFileTool(
 							cline,
 							block,

src/core/prompts/__tests__/__snapshots__/add-custom-instructions/architect-mode-prompt.snap

@@ -385,10 +385,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/add-custom-instructions/ask-mode-prompt.snap

@@ -318,10 +318,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/add-custom-instructions/mcp-server-creation-disabled.snap

@@ -384,10 +384,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/add-custom-instructions/mcp-server-creation-enabled.snap

@@ -434,10 +434,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/add-custom-instructions/partial-reads-enabled.snap

@@ -390,10 +390,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/consistent-system-prompt.snap

@@ -385,10 +385,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-computer-use-support.snap

@@ -453,10 +453,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-false.snap

@@ -385,10 +385,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-true.snap

@@ -473,10 +473,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-diff-enabled-undefined.snap

@@ -385,10 +385,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-different-viewport-size.snap

@@ -385,10 +385,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-mcp-hub-provided.snap

@@ -434,10 +434,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/__tests__/__snapshots__/system-prompt/with-undefined-mcp-hub.snap

@@ -385,10 +385,10 @@ Replace the entire TODO list with an updated checklist reflecting the current st
 3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
 4. Formulate your tool use using the XML format specified for each tool.
 5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.
 6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
 
 It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:

src/core/prompts/sections/tool-use-guidelines.ts

@@ -35,34 +35,48 @@ export function getToolUseGuidelinesSection(
 		)
 	}
 
-	// Remaining guidelines
-	guidelinesList.push(
-		`${itemNumber++}. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.`,
-	)
+	// Remaining guidelines - different for native vs XML protocol
+	if (isNativeProtocol(protocol)) {
+		guidelinesList.push(
+			`${itemNumber++}. If multiple actions are needed, you may use multiple tools in a single message when appropriate, or use tools iteratively across messages. Each tool use should be informed by the results of previous tool uses. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.`,
+		)
+	} else {
+		guidelinesList.push(
+			`${itemNumber++}. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.`,
+		)
+	}
 
 	// Protocol-specific guideline - only add for XML protocol
 	if (!isNativeProtocol(protocol)) {
 		guidelinesList.push(`${itemNumber++}. Formulate your tool use using the XML format specified for each tool.`)
 	}
 	guidelinesList.push(`${itemNumber++}. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.`)
-	guidelinesList.push(
-		`${itemNumber++}. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.`,
-	)
+	 - Information about whether the tool succeeded or failed, along with any reasons for failure.
+	 - Linter errors that may have arisen due to the changes you made, which you'll need to address.
+	 - New terminal output in reaction to the changes, which you may need to consider or act upon.
+	 - Any other relevant feedback or information related to the tool use.`)
 
-	// Join guidelines and add the footer
-	return `# Tool Use Guidelines
-
-${guidelinesList.join("\n")}
+	// Only add the "wait for confirmation" guideline for XML protocol
+	// Native protocol allows multiple tools per message, so waiting after each tool doesn't apply
+	if (!isNativeProtocol(protocol)) {
+		guidelinesList.push(
+			`${itemNumber++}. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.`,
+		)
+	}
 
-It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:
+	// Join guidelines and add the footer
+	// For native protocol, the footer is less relevant since multiple tools can execute in one message
+	const footer = isNativeProtocol(protocol)
+		? `\n\nBy carefully considering the user's response after tool executions, you can react accordingly and make informed decisions about how to proceed with the task. This iterative process helps ensure the overall success and accuracy of your work.`
+		: `\n\nIt is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:
 1. Confirm the success of each step before proceeding.
 2. Address any issues or errors that arise immediately.
 3. Adapt your approach based on new information or unexpected results.
 4. Ensure that each action builds correctly on the previous ones.
 
 By waiting for and carefully considering the user's response after each tool use, you can react accordingly and make informed decisions about how to proceed with the task. This iterative process helps ensure the overall success and accuracy of your work.`
+
+	return `# Tool Use Guidelines
+
+${guidelinesList.join("\n")}${footer}`
 }

src/core/task/Task.ts

@@ -302,6 +302,7 @@ export class Task extends EventEmitter<TaskEvents> implements TaskLike {
 	userMessageContentReady = false
 	didRejectTool = false
 	didAlreadyUseTool = false
+	didToolFailInCurrentTurn = false
 	didCompleteReadingStream = false
 	assistantMessageParser?: AssistantMessageParser
 	private providerProfileChangeListener?: (config: { name: string; provider?: string }) => void
@@ -2255,6 +2256,10 @@ export class Task extends EventEmitter<TaskEvents> implements TaskLike {
 				this.userMessageContentReady = false
 				this.didRejectTool = false
 				this.didAlreadyUseTool = false
+				// Reset tool failure flag for each new assistant turn - this ensures that tool failures
+				// only prevent attempt_completion within the same assistant message, not across turns
+				// (e.g., if a tool fails, then user sends a message saying "just complete anyway")
+				this.didToolFailInCurrentTurn = false
 				this.presentAssistantMessageLocked = false
 				this.presentAssistantMessageHasPendingUpdates = false
 				this.assistantMessageParser?.reset()
@@ -2464,7 +2469,8 @@ export class Task extends EventEmitter<TaskEvents> implements TaskLike {
 								// Mark that we have new content to process
 								this.userMessageContentReady = false
 
-								// Present the tool call to user
+								// Present the tool call to user - presentAssistantMessage will execute
+								// tools sequentially and accumulate all results in userMessageContent
 								presentAssistantMessage(this)
 								break
 							}
@@ -2840,12 +2846,12 @@ export class Task extends EventEmitter<TaskEvents> implements TaskLike {
 					this.assistantMessageContent = parsedBlocks
 				}
 
-				if (partialBlocks.length > 0) {
+				// Only present partial blocks that were just completed (from XML parsing)
+				// Native tool blocks were already presented during streaming, so don't re-present them
+				if (partialBlocks.length > 0 && partialBlocks.some((block) => block.type !== "tool_use")) {
 					// If there is content to update then it will complete and
 					// update `this.userMessageContentReady` to true, which we
-					// `pWaitFor` before making the next request. All this is really
-					// doing is presenting the last partial message that we just set
-					// to complete.
+					// `pWaitFor` before making the next request.
 					presentAssistantMessage(this)
 				}
 

src/core/tools/ApplyDiffTool.ts

@@ -70,6 +70,7 @@ export class ApplyDiffTool extends BaseTool<"apply_diff"> {
 				task.recordToolError("apply_diff")
 				const formattedError = `File does not exist at path: ${absolutePath}\n\n<error_details>\nThe specified file could not be found. Please verify the file path and try again.\n</error_details>`
 				await task.say("error", formattedError)
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formattedError)
 				return
 			}

src/core/tools/AskFollowupQuestionTool.ts

@@ -71,6 +71,7 @@ export class AskFollowupQuestionTool extends BaseTool<"ask_followup_question"> {
 			if (!question) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("ask_followup_question")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("ask_followup_question", "question"))
 				return
 			}

src/core/tools/AttemptCompletionTool.ts

@@ -9,6 +9,7 @@ import { formatResponse } from "../prompts/responses"
 import { Package } from "../../shared/package"
 import { BaseTool, ToolCallbacks } from "./BaseTool"
 import type { ToolUse } from "../../shared/tools"
+import { t } from "../../i18n"
 
 interface AttemptCompletionParams {
 	result: string
@@ -34,6 +35,15 @@ export class AttemptCompletionTool extends BaseTool<"attempt_completion"> {
 		const { result } = params
 		const { handleError, pushToolResult, askFinishSubTaskApproval, toolDescription, toolProtocol } = callbacks
 
+		// Prevent attempt_completion if any tool failed in the current turn
+		if (task.didToolFailInCurrentTurn) {
+			const errorMsg = t("common:errors.attempt_completion_tool_failed")
+
+			await task.say("error", errorMsg)
+			pushToolResult(formatResponse.toolError(errorMsg))
+			return
+		}
+
 		const preventCompletionWithOpenTodos = vscode.workspace
 			.getConfiguration(Package.name)
 			.get<boolean>("preventCompletionWithOpenTodos", false)

src/core/tools/BrowserActionTool.ts

@@ -30,6 +30,7 @@ export async function browserActionTool(
 			// if the block is complete and we don't have a valid action cline is a mistake
 			cline.consecutiveMistakeCount++
 			cline.recordToolError("browser_action")
+			cline.didToolFailInCurrentTurn = true
 			pushToolResult(await cline.sayAndCreateMissingParamError("browser_action", "action"))
 			// Do not close the browser on parameter validation errors
 		}
@@ -63,6 +64,7 @@ export async function browserActionTool(
 				if (!url) {
 					cline.consecutiveMistakeCount++
 					cline.recordToolError("browser_action")
+					cline.didToolFailInCurrentTurn = true
 					pushToolResult(await cline.sayAndCreateMissingParamError("browser_action", "url"))
 					// Do not close the browser on parameter validation errors
 					return
@@ -102,22 +104,24 @@ export async function browserActionTool(
 					if (!coordinate) {
 						cline.consecutiveMistakeCount++
 						cline.recordToolError("browser_action")
+						cline.didToolFailInCurrentTurn = true
 						pushToolResult(await cline.sayAndCreateMissingParamError("browser_action", "coordinate"))
 						// Do not close the browser on parameter validation errors
 						return // can't be within an inner switch
 					}
-
+	
 					// Get viewport dimensions from the browser session
 					const viewportSize = cline.browserSession.getViewportSize()
 					const viewportWidth = viewportSize.width || 900 // default to 900 if not available
 					const viewportHeight = viewportSize.height || 600 // default to 600 if not available
-
+	
 					// Scale coordinate from image dimensions to viewport dimensions
 					try {
 						processedCoordinate = scaleCoordinate(coordinate, viewportWidth, viewportHeight)
 					} catch (error) {
 						cline.consecutiveMistakeCount++
 						cline.recordToolError("browser_action")
+						cline.didToolFailInCurrentTurn = true
 						pushToolResult(
 							await cline.sayAndCreateMissingParamError(
 								"browser_action",
@@ -133,16 +137,18 @@ export async function browserActionTool(
 					if (!text) {
 						cline.consecutiveMistakeCount++
 						cline.recordToolError("browser_action")
+						cline.didToolFailInCurrentTurn = true
 						pushToolResult(await cline.sayAndCreateMissingParamError("browser_action", "text"))
 						// Do not close the browser on parameter validation errors
 						return
 					}
 				}
-
+	
 				if (action === "resize") {
 					if (!size) {
 						cline.consecutiveMistakeCount++
 						cline.recordToolError("browser_action")
+						cline.didToolFailInCurrentTurn = true
 						pushToolResult(await cline.sayAndCreateMissingParamError("browser_action", "size"))
 						// Do not close the browser on parameter validation errors
 						return

src/core/tools/CodebaseSearchTool.ts

@@ -44,6 +44,7 @@ export class CodebaseSearchTool extends BaseTool<"codebase_search"> {
 
 		if (!query) {
 			task.consecutiveMistakeCount++
+			task.didToolFailInCurrentTurn = true
 			pushToolResult(await task.sayAndCreateMissingParamError("codebase_search", "query"))
 			return
 		}

src/core/tools/ExecuteCommandTool.ts

@@ -291,6 +291,7 @@ export async function executeCommandInTerminal(
 				const status: CommandExecutionStatus = { executionId, status: "timeout" }
 				provider?.postMessageToWebview({ type: "commandExecutionStatus", text: JSON.stringify(status) })
 				await task.say("error", t("common:errors:command_timeout", { seconds: commandExecutionTimeoutSeconds }))
+				task.didToolFailInCurrentTurn = true
 				task.terminalProcess = undefined
 
 				return [

src/core/tools/FetchInstructionsTool.ts

@@ -26,6 +26,7 @@ export class FetchInstructionsTool extends BaseTool<"fetch_instructions"> {
 			if (!taskParam) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("fetch_instructions")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("fetch_instructions", "task"))
 				return
 			}

src/core/tools/GenerateImageTool.ts

@@ -78,6 +78,7 @@ export class GenerateImageTool extends BaseTool<"generate_image"> {
 			const inputImageExists = await fileExistsAtPath(inputImageFullPath)
 			if (!inputImageExists) {
 				await task.say("error", `Input image not found: ${getReadablePath(task.cwd, inputImagePath)}`)
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(
 					formatResponse.toolError(`Input image not found: ${getReadablePath(task.cwd, inputImagePath)}`),
 				)
@@ -101,6 +102,7 @@ export class GenerateImageTool extends BaseTool<"generate_image"> {
 						"error",
 						`Unsupported image format: ${imageExtension}. Supported formats: ${supportedFormats.join(", ")}`,
 					)
+					task.didToolFailInCurrentTurn = true
 					pushToolResult(
 						formatResponse.toolError(
 							`Unsupported image format: ${imageExtension}. Supported formats: ${supportedFormats.join(", ")}`,
@@ -116,6 +118,7 @@ export class GenerateImageTool extends BaseTool<"generate_image"> {
 					"error",
 					`Failed to read input image: ${error instanceof Error ? error.message : "Unknown error"}`,
 				)
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(
 					formatResponse.toolError(
 						`Failed to read input image: ${error instanceof Error ? error.message : "Unknown error"}`,
@@ -207,6 +210,7 @@ export class GenerateImageTool extends BaseTool<"generate_image"> {
 
 			if (!result.success) {
 				await task.say("error", result.error || "Failed to generate image")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formatResponse.toolError(result.error || "Failed to generate image"))
 				return
 			}
@@ -214,6 +218,7 @@ export class GenerateImageTool extends BaseTool<"generate_image"> {
 			if (!result.imageData) {
 				const errorMessage = "No image data received"
 				await task.say("error", errorMessage)
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formatResponse.toolError(errorMessage))
 				return
 			}
@@ -222,6 +227,7 @@ export class GenerateImageTool extends BaseTool<"generate_image"> {
 			if (!base64Match) {
 				const errorMessage = "Invalid image format received"
 				await task.say("error", errorMessage)
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formatResponse.toolError(errorMessage))
 				return
 			}

src/core/tools/InsertContentTool.ts

@@ -85,6 +85,7 @@ export class InsertContentTool extends BaseTool<"insert_content"> {
 					task.recordToolError("insert_content")
 					const formattedError = `Cannot insert content at line ${lineNumber} into a non-existent file. For new files, 'line' must be 0 (to append) or 1 (to insert at the beginning).`
 					await task.say("error", formattedError)
+					task.didToolFailInCurrentTurn = true
 					pushToolResult(formattedError)
 					return
 				}

src/core/tools/ListCodeDefinitionNamesTool.ts

@@ -31,6 +31,7 @@ export class ListCodeDefinitionNamesTool extends BaseTool<"list_code_definition_
 		if (!relPath) {
 			task.consecutiveMistakeCount++
 			task.recordToolError("list_code_definition_names")
+			task.didToolFailInCurrentTurn = true
 			pushToolResult(await task.sayAndCreateMissingParamError("list_code_definition_names", "path"))
 			return
 		}

src/core/tools/ListFilesTool.ts

@@ -35,6 +35,7 @@ export class ListFilesTool extends BaseTool<"list_files"> {
 			if (!relDirPath) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("list_files")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("list_files", "path"))
 				return
 			}

src/core/tools/NewTaskTool.ts

@@ -37,6 +37,7 @@ export class NewTaskTool extends BaseTool<"new_task"> {
 			if (!mode) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("new_task")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("new_task", "mode"))
 				return
 			}
@@ -44,6 +45,7 @@ export class NewTaskTool extends BaseTool<"new_task"> {
 			if (!message) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("new_task")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("new_task", "message"))
 				return
 			}
@@ -69,6 +71,7 @@ export class NewTaskTool extends BaseTool<"new_task"> {
 			if (requireTodos && todos === undefined) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("new_task")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("new_task", "todos"))
 				return
 			}
@@ -81,6 +84,7 @@ export class NewTaskTool extends BaseTool<"new_task"> {
 				} catch (error) {
 					task.consecutiveMistakeCount++
 					task.recordToolError("new_task")
+					task.didToolFailInCurrentTurn = true
 					pushToolResult(formatResponse.toolError("Invalid todos format: must be a markdown checklist"))
 					return
 				}

src/core/tools/ReadFileTool.ts

@@ -543,6 +543,12 @@ export class ReadFileTool extends BaseTool<"read_file"> {
 				}
 			}
 
+			// Check if any files had errors or were blocked and mark the turn as failed
+			const hasErrors = fileResults.some((result) => result.status === "error" || result.status === "blocked")
+			if (hasErrors) {
+				task.didToolFailInCurrentTurn = true
+			}
+
 			// Build final result based on protocol
 			let finalResult: string
 			if (useNative) {
@@ -623,6 +629,9 @@ export class ReadFileTool extends BaseTool<"read_file"> {
 
 			await task.say("error", `Error reading file ${relPath}: ${errorMsg}`)
 
+			// Mark that a tool failed in this turn
+			task.didToolFailInCurrentTurn = true
+
 			// Build final error result based on protocol
 			let errorResult: string
 			if (useNative) {

src/core/tools/RunSlashCommandTool.ts

@@ -45,6 +45,7 @@ export class RunSlashCommandTool extends BaseTool<"run_slash_command"> {
 			if (!commandName) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("run_slash_command")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(await task.sayAndCreateMissingParamError("run_slash_command", "command"))
 				return
 			}
@@ -58,6 +59,7 @@ export class RunSlashCommandTool extends BaseTool<"run_slash_command"> {
 				// Get available commands for error message
 				const availableCommands = await getCommandNames(task.cwd)
 				task.recordToolError("run_slash_command")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(
 					formatResponse.toolError(
 						`Command '${commandName}' not found. Available commands: ${availableCommands.join(", ") || "(none)"}`,

src/core/tools/SearchFilesTool.ts

@@ -35,6 +35,7 @@ export class SearchFilesTool extends BaseTool<"search_files"> {
 		if (!relDirPath) {
 			task.consecutiveMistakeCount++
 			task.recordToolError("search_files")
+			task.didToolFailInCurrentTurn = true
 			pushToolResult(await task.sayAndCreateMissingParamError("search_files", "path"))
 			return
 		}
@@ -42,6 +43,7 @@ export class SearchFilesTool extends BaseTool<"search_files"> {
 		if (!regex) {
 			task.consecutiveMistakeCount++
 			task.recordToolError("search_files")
+			task.didToolFailInCurrentTurn = true
 			pushToolResult(await task.sayAndCreateMissingParamError("search_files", "regex"))
 			return
 		}

src/core/tools/SwitchModeTool.ts

@@ -40,6 +40,7 @@ export class SwitchModeTool extends BaseTool<"switch_mode"> {
 
 			if (!targetMode) {
 				task.recordToolError("switch_mode")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formatResponse.toolError(`Invalid mode: ${mode_slug}`))
 				return
 			}
@@ -49,6 +50,7 @@ export class SwitchModeTool extends BaseTool<"switch_mode"> {
 
 			if (currentMode === mode_slug) {
 				task.recordToolError("switch_mode")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(`Already in ${targetMode.name} mode.`)
 				return
 			}

src/core/tools/UpdateTodoListTool.ts

@@ -34,6 +34,7 @@ export class UpdateTodoListTool extends BaseTool<"update_todo_list"> {
 			} catch {
 				task.consecutiveMistakeCount++
 				task.recordToolError("update_todo_list")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formatResponse.toolError("The todos parameter is not valid markdown checklist or JSON"))
 				return
 			}
@@ -42,6 +43,7 @@ export class UpdateTodoListTool extends BaseTool<"update_todo_list"> {
 			if (!valid) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("update_todo_list")
+				task.didToolFailInCurrentTurn = true
 				pushToolResult(formatResponse.toolError(error || "todos parameter validation failed"))
 				return
 			}

src/core/tools/UseMcpToolTool.ts

@@ -130,6 +130,7 @@ export class UseMcpToolTool extends BaseTool<"use_mcp_tool"> {
 					task.consecutiveMistakeCount++
 					task.recordToolError("use_mcp_tool")
 					await task.say("error", t("mcp:errors.invalidJsonArgument", { toolName: params.tool_name }))
+					task.didToolFailInCurrentTurn = true
 
 					pushToolResult(
 						formatResponse.toolError(
@@ -178,6 +179,7 @@ export class UseMcpToolTool extends BaseTool<"use_mcp_tool"> {
 				task.consecutiveMistakeCount++
 				task.recordToolError("use_mcp_tool")
 				await task.say("error", t("mcp:errors.serverNotFound", { serverName, availableServers }))
+				task.didToolFailInCurrentTurn = true
 
 				pushToolResult(formatResponse.unknownMcpServerError(serverName, availableServersArray))
 				return { isValid: false, availableTools: [] }
@@ -196,6 +198,7 @@ export class UseMcpToolTool extends BaseTool<"use_mcp_tool"> {
 						availableTools: "No tools available",
 					}),
 				)
+				task.didToolFailInCurrentTurn = true
 
 				pushToolResult(formatResponse.unknownMcpToolError(serverName, toolName, []))
 				return { isValid: false, availableTools: [] }
@@ -218,6 +221,7 @@ export class UseMcpToolTool extends BaseTool<"use_mcp_tool"> {
 						availableTools: availableToolNames.join(", "),
 					}),
 				)
+				task.didToolFailInCurrentTurn = true
 
 				pushToolResult(formatResponse.unknownMcpToolError(serverName, toolName, availableToolNames))
 				return { isValid: false, availableTools: availableToolNames }
@@ -240,6 +244,7 @@ export class UseMcpToolTool extends BaseTool<"use_mcp_tool"> {
 							enabledToolNames.length > 0 ? enabledToolNames.join(", ") : "No enabled tools available",
 					}),
 				)
+				task.didToolFailInCurrentTurn = true
 
 				pushToolResult(formatResponse.unknownMcpToolError(serverName, toolName, enabledToolNames))
 				return { isValid: false, availableTools: enabledToolNames }

src/core/tools/WriteToFileTool.ts

@@ -106,6 +106,7 @@ export class WriteToFileTool extends BaseTool<"write_to_file"> {
 			if (predictedLineCount === undefined || predictedLineCount === 0) {
 				task.consecutiveMistakeCount++
 				task.recordToolError("write_to_file")
+				task.didToolFailInCurrentTurn = true
 
 				const actualLineCount = newContent.split("\n").length
 				const isNewFile = !fileExists

src/core/tools/__tests__/attemptCompletionTool.spec.ts

@@ -408,5 +408,69 @@ describe("attemptCompletionTool", () => {
 				expect.stringContaining("Cannot complete task while there are incomplete todos"),
 			)
 		})
+
+		describe("tool failure guardrail", () => {
+			it("should prevent completion when a previous tool failed in the current turn", async () => {
+				const block: AttemptCompletionToolUse = {
+					type: "tool_use",
+					name: "attempt_completion",
+					params: { result: "Task completed successfully" },
+					partial: false,
+				}
+
+				mockTask.todoList = undefined
+				mockTask.didToolFailInCurrentTurn = true
+
+				const callbacks: AttemptCompletionCallbacks = {
+					askApproval: mockAskApproval,
+					handleError: mockHandleError,
+					pushToolResult: mockPushToolResult,
+					removeClosingTag: mockRemoveClosingTag,
+					askFinishSubTaskApproval: mockAskFinishSubTaskApproval,
+					toolDescription: mockToolDescription,
+					toolProtocol: "xml",
+				}
+
+				const mockSay = vi.fn()
+				mockTask.say = mockSay
+
+				await attemptCompletionTool.handle(mockTask as Task, block, callbacks)
+
+				expect(mockSay).toHaveBeenCalledWith(
+					"error",
+					expect.stringContaining("errors.attempt_completion_tool_failed"),
+				)
+				expect(mockPushToolResult).toHaveBeenCalledWith(
+					expect.stringContaining("errors.attempt_completion_tool_failed"),
+				)
+			})
+
+			it("should allow completion when no tools failed", async () => {
+				const block: AttemptCompletionToolUse = {
+					type: "tool_use",
+					name: "attempt_completion",
+					params: { result: "Task completed successfully" },
+					partial: false,
+				}
+
+				mockTask.todoList = undefined
+				mockTask.didToolFailInCurrentTurn = false
+
+				const callbacks: AttemptCompletionCallbacks = {
+					askApproval: mockAskApproval,
+					handleError: mockHandleError,
+					pushToolResult: mockPushToolResult,
+					removeClosingTag: mockRemoveClosingTag,
+					askFinishSubTaskApproval: mockAskFinishSubTaskApproval,
+					toolDescription: mockToolDescription,
+					toolProtocol: "xml",
+				}
+
+				await attemptCompletionTool.handle(mockTask as Task, block, callbacks)
+
+				expect(mockTask.consecutiveMistakeCount).toBe(0)
+				expect(mockTask.recordToolError).not.toHaveBeenCalled()
+			})
+		})
 	})
 })

src/shared/__tests__/experiments.spec.ts

@@ -31,6 +31,7 @@ describe("experiments", () => {
 				preventFocusDisruption: false,
 				imageGeneration: false,
 				runSlashCommand: false,
+				multipleNativeToolCalls: false,
 			}
 			expect(Experiments.isEnabled(experiments, EXPERIMENT_IDS.POWER_STEERING)).toBe(false)
 		})
@@ -42,6 +43,7 @@ describe("experiments", () => {
 				preventFocusDisruption: false,
 				imageGeneration: false,
 				runSlashCommand: false,
+				multipleNativeToolCalls: false,
 			}
 			expect(Experiments.isEnabled(experiments, EXPERIMENT_IDS.POWER_STEERING)).toBe(true)
 		})
@@ -53,6 +55,7 @@ describe("experiments", () => {
 				preventFocusDisruption: false,
 				imageGeneration: false,
 				runSlashCommand: false,
+				multipleNativeToolCalls: false,
 			}
 			expect(Experiments.isEnabled(experiments, EXPERIMENT_IDS.POWER_STEERING)).toBe(false)
 		})

src/shared/experiments.ts

@@ -6,6 +6,7 @@ export const EXPERIMENT_IDS = {
 	PREVENT_FOCUS_DISRUPTION: "preventFocusDisruption",
 	IMAGE_GENERATION: "imageGeneration",
 	RUN_SLASH_COMMAND: "runSlashCommand",
+	MULTIPLE_NATIVE_TOOL_CALLS: "multipleNativeToolCalls",
 } as const satisfies Record<string, ExperimentId>
 
 type _AssertExperimentIds = AssertEqual<Equals<ExperimentId, Values<typeof EXPERIMENT_IDS>>>
@@ -22,6 +23,7 @@ export const experimentConfigsMap: Record<ExperimentKey, ExperimentConfig> = {
 	PREVENT_FOCUS_DISRUPTION: { enabled: false },
 	IMAGE_GENERATION: { enabled: false },
 	RUN_SLASH_COMMAND: { enabled: false },
+	MULTIPLE_NATIVE_TOOL_CALLS: { enabled: false },
 }
 
 export const experimentDefault = Object.fromEntries(

webview-ui/src/context/__tests__/ExtensionStateContext.spec.tsx

@@ -239,6 +239,7 @@ describe("mergeExtensionState", () => {
 				imageGeneration: false,
 				runSlashCommand: false,
 				nativeToolCalling: false,
+				multipleNativeToolCalls: false,
 			} as Record<ExperimentId, boolean>,
 			checkpointTimeout: DEFAULT_CHECKPOINT_TIMEOUT_SECONDS + 5,
 		}
@@ -261,6 +262,7 @@ describe("mergeExtensionState", () => {
 			imageGeneration: false,
 			runSlashCommand: false,
 			nativeToolCalling: false,
+			multipleNativeToolCalls: false,
 		})
 	})
 })

webview-ui/src/i18n/locales/ca/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Has esperat {{timeout}} segons per inicialitzar el punt de control. Si no necessites aquesta funció, desactiva-la a <settingsLink>la configuració del punt de control</settingsLink>.",
-		"init_checkpoint_fail_long_time": "La inicialització del punt de control ha trigat més de {{timeout}} segons, per això els punts de control estan desactivats per a aquesta tasca. Pots desactivar els punts de control o augmentar el temps d'espera a <settingsLink>la configuració del punt de control</settingsLink>."
+		"init_checkpoint_fail_long_time": "La inicialització del punt de control ha trigat més de {{timeout}} segons, per això els punts de control estan desactivats per a aquesta tasca. Pots desactivar els punts de control o augmentar el temps d'espera a <settingsLink>la configuració del punt de control</settingsLink>.",
+		"attempt_completion_tool_failed": "No es pot executar attempt_completion perquè una crida d'eina anterior ha fallat en aquest torn. Si us plau, resol el problema de l'eina abans d'intentar completar."
 	}
 }

webview-ui/src/i18n/locales/ca/settings.json

@@ -809,6 +809,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Habilitar comandes de barra diagonal iniciades pel model",
 			"description": "Quan està habilitat, Roo pot executar les vostres comandes de barra diagonal per executar fluxos de treball."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Crides paral·leles a eines",
+			"description": "Quan està activat, el protocol natiu pot executar múltiples eines en un sol torn de missatge de l'assistent."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/de/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Du hast {{timeout}} Sekunden auf die Initialisierung des Checkpoints gewartet. Wenn du die Checkpoint-Funktion nicht brauchst, kannst du sie in den <settingsLink>Checkpoint-Einstellungen</settingsLink> ausschalten.",
-		"init_checkpoint_fail_long_time": "Die Initialisierung des Checkpoints dauert länger als {{timeout}} Sekunden, deshalb sind Checkpoints für diese Aufgabe deaktiviert. Du kannst Checkpoints ausschalten oder die Wartezeit in den <settingsLink>Checkpoint-Einstellungen</settingsLink> verlängern."
+		"init_checkpoint_fail_long_time": "Die Initialisierung des Checkpoints dauert länger als {{timeout}} Sekunden, deshalb sind Checkpoints für diese Aufgabe deaktiviert. Du kannst Checkpoints ausschalten oder die Wartezeit in den <settingsLink>Checkpoint-Einstellungen</settingsLink> verlängern.",
+		"attempt_completion_tool_failed": "Du kannst attempt_completion nicht ausführen, weil ein vorheriger Tool-Aufruf in diesem Durchgang fehlgeschlagen ist. Behebe den Tool-Fehler, bevor du versuchst, abzuschließen."
 	}
 }

webview-ui/src/i18n/locales/de/settings.json

@@ -809,6 +809,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Modellinitierte Slash-Befehle aktivieren",
 			"description": "Wenn aktiviert, kann Roo deine Slash-Befehle ausführen, um Workflows zu starten."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Parallele Tool-Aufrufe",
+			"description": "Wenn aktiviert, kann das native Protokoll mehrere Tools in einer einzigen Assistenten-Nachrichtenrunde ausführen."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/en/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Waited {{timeout}} seconds for checkpoint initialization. If you don't need the checkpoint feature, please turn it off in <settingsLink>the checkpoint settings</settingsLink>.",
-		"init_checkpoint_fail_long_time": "Checkpoint initialization has taken more than {{timeout}} seconds, so checkpoints are disabled for this task. You can disable checkpoints or extend the waiting time in <settingsLink>the checkpoint settings</settingsLink>."
+		"init_checkpoint_fail_long_time": "Checkpoint initialization has taken more than {{timeout}} seconds, so checkpoints are disabled for this task. You can disable checkpoints or extend the waiting time in <settingsLink>the checkpoint settings</settingsLink>.",
+		"attempt_completion_tool_failed": "Cannot execute attempt_completion because a previous tool call failed in this turn. Please address the tool failure before attempting completion."
 	}
 }

webview-ui/src/i18n/locales/en/settings.json

@@ -814,6 +814,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Enable model-initiated slash commands",
 			"description": "When enabled, Roo can run your slash commands to execute workflows."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Parallel tool calls",
+			"description": "When enabled, the native protocol can execute multiple tools in a single assistant message turn."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/es/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Has esperado {{timeout}} segundos para la inicialización del punto de control. Si no necesitas esta función, desactívala en <settingsLink>la configuración del punto de control</settingsLink>.",
-		"init_checkpoint_fail_long_time": "La inicialización del punto de control ha tardado más de {{timeout}} segundos, por lo que los puntos de control están desactivados para esta tarea. Puedes desactivar los puntos de control o aumentar el tiempo de espera en <settingsLink>la configuración del punto de control</settingsLink>."
+		"init_checkpoint_fail_long_time": "La inicialización del punto de control ha tardado más de {{timeout}} segundos, por lo que los puntos de control están desactivados para esta tarea. Puedes desactivar los puntos de control o aumentar el tiempo de espera en <settingsLink>la configuración del punto de control</settingsLink>.",
+		"attempt_completion_tool_failed": "No se puede ejecutar attempt_completion porque una llamada de herramienta anterior falló en este turno. Por favor, resuelve el error de la herramienta antes de intentar completar."
 	}
 }

webview-ui/src/i18n/locales/es/settings.json

@@ -809,6 +809,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Habilitar comandos slash iniciados por el modelo",
 			"description": "Cuando está habilitado, Roo puede ejecutar tus comandos slash para ejecutar flujos de trabajo."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Llamadas paralelas a herramientas",
+			"description": "Cuando está habilitado, el protocolo nativo puede ejecutar múltiples herramientas en un solo turno de mensaje del asistente."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/fr/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Tu as attendu {{timeout}} secondes pour l'initialisation du checkpoint. Si tu n'as pas besoin de cette fonction, désactive-la dans <settingsLink>les paramètres du checkpoint</settingsLink>.",
-		"init_checkpoint_fail_long_time": "L'initialisation du checkpoint a pris plus de {{timeout}} secondes, donc les checkpoints sont désactivés pour cette tâche. Tu peux désactiver les checkpoints ou prolonger le délai dans <settingsLink>les paramètres du checkpoint</settingsLink>."
+		"init_checkpoint_fail_long_time": "L'initialisation du checkpoint a pris plus de {{timeout}} secondes, donc les checkpoints sont désactivés pour cette tâche. Tu peux désactiver les checkpoints ou prolonger le délai dans <settingsLink>les paramètres du checkpoint</settingsLink>.",
+		"attempt_completion_tool_failed": "Tu ne peux pas exécuter attempt_completion car un appel d'outil précédent a échoué dans ce tour. Résous l'échec de l'outil avant de tenter de terminer."
 	}
 }

webview-ui/src/i18n/locales/fr/settings.json

@@ -809,6 +809,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Activer les commandes slash initiées par le modèle",
 			"description": "Lorsque activé, Roo peut exécuter tes commandes slash pour lancer des workflows."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Appels d'outils parallèles",
+			"description": "Lorsqu'activé, le protocole natif peut exécuter plusieurs outils en un seul tour de message d'assistant."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/hi/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "तुमने {{timeout}} सेकंड तक चेकपॉइंट इनिशियलाइज़ेशन का इंतजार किया। अगर तुम्हें यह फ़ीचर नहीं चाहिए, तो <settingsLink>चेकपॉइंट सेटिंग्स</settingsLink> में बंद कर दो।",
-		"init_checkpoint_fail_long_time": "चेकपॉइंट इनिशियलाइज़ेशन {{timeout}} सेकंड से ज़्यादा समय ले रहा है, इसलिए इस कार्य के लिए चेकपॉइंट बंद कर दिए गए हैं। तुम चेकपॉइंट बंद कर सकते हो या <settingsLink>चेकपॉइंट सेटिंग्स</settingsLink> में इंतजार का समय बढ़ा सकते हो।"
+		"init_checkpoint_fail_long_time": "चेकपॉइंट इनिशियलाइज़ेशन {{timeout}} सेकंड से ज़्यादा समय ले रहा है, इसलिए इस कार्य के लिए चेकपॉइंट बंद कर दिए गए हैं। तुम चेकपॉइंट बंद कर सकते हो या <settingsLink>चेकपॉइंट सेटिंग्स</settingsLink> में इंतजार का समय बढ़ा सकते हो।",
+		"attempt_completion_tool_failed": "attempt_completion निष्पादित नहीं किया जा सकता क्योंकि इस टर्न में पिछली टूल कॉल विफल रही है। कृपया पूरा करने का प्रयास करने से पहले टूल विफलता को ठीक करें।"
 	}
 }

webview-ui/src/i18n/locales/hi/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "मॉडल द्वारा शुरू किए गए स्लैश कमांड सक्षम करें",
 			"description": "जब सक्षम होता है, Roo वर्कफ़्लो चलाने के लिए आपके स्लैश कमांड चला सकता है।"
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "समानांतर टूल कॉल",
+			"description": "सक्षम होने पर, नेटिव प्रोटोकॉल एकल सहायक संदेश टर्न में एकाधिक टूल निष्पादित कर सकता है।"
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/id/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Kamu sudah menunggu {{timeout}} detik untuk inisialisasi checkpoint. Kalau tidak butuh fitur ini, matikan saja di <settingsLink>pengaturan checkpoint</settingsLink>.",
-		"init_checkpoint_fail_long_time": "Inisialisasi checkpoint sudah lebih dari {{timeout}} detik, jadi checkpoint dinonaktifkan untuk tugas ini. Kamu bisa mematikan checkpoint atau menambah waktu tunggu di <settingsLink>pengaturan checkpoint</settingsLink>."
+		"init_checkpoint_fail_long_time": "Inisialisasi checkpoint sudah lebih dari {{timeout}} detik, jadi checkpoint dinonaktifkan untuk tugas ini. Kamu bisa mematikan checkpoint atau menambah waktu tunggu di <settingsLink>pengaturan checkpoint</settingsLink>.",
+		"attempt_completion_tool_failed": "Tidak dapat mengeksekusi attempt_completion karena panggilan alat sebelumnya gagal dalam giliran ini. Harap atasi kegagalan alat sebelum mencoba menyelesaikan."
 	}
 }

webview-ui/src/i18n/locales/id/settings.json

@@ -839,6 +839,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Aktifkan perintah slash yang dimulai model",
 			"description": "Ketika diaktifkan, Roo dapat menjalankan perintah slash Anda untuk mengeksekusi alur kerja."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Panggilan tool paralel",
+			"description": "Ketika diaktifkan, protokol native dapat mengeksekusi beberapa tool dalam satu giliran pesan asisten."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/it/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Hai aspettato {{timeout}} secondi per l'inizializzazione del checkpoint. Se non ti serve questa funzione, disattivala nelle <settingsLink>impostazioni del checkpoint</settingsLink>.",
-		"init_checkpoint_fail_long_time": "L'inizializzazione del checkpoint ha impiegato più di {{timeout}} secondi, quindi i checkpoint sono disabilitati per questa attività. Puoi disattivare i checkpoint o aumentare il tempo di attesa nelle <settingsLink>impostazioni del checkpoint</settingsLink>."
+		"init_checkpoint_fail_long_time": "L'inizializzazione del checkpoint ha impiegato più di {{timeout}} secondi, quindi i checkpoint sono disabilitati per questa attività. Puoi disattivare i checkpoint o aumentare il tempo di attesa nelle <settingsLink>impostazioni del checkpoint</settingsLink>.",
+		"attempt_completion_tool_failed": "Non puoi eseguire attempt_completion perché una chiamata di strumento precedente è fallita in questo turno. Risolvi il problema dello strumento prima di tentare di completare."
 	}
 }

webview-ui/src/i18n/locales/it/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Abilita comandi slash avviati dal modello",
 			"description": "Quando abilitato, Roo può eseguire i tuoi comandi slash per eseguire flussi di lavoro."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Chiamate parallele agli strumenti",
+			"description": "Quando abilitato, il protocollo nativo può eseguire più strumenti in un singolo turno di messaggio dell'assistente."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/ja/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "{{timeout}} 秒間チェックポイントの初期化を待機しました。チェックポイント機能が不要な場合は、<settingsLink>チェックポイント設定</settingsLink>でオフにしてください。",
-		"init_checkpoint_fail_long_time": "チェックポイントの初期化が {{timeout}} 秒以上かかったため、このタスクではチェックポイントが無効化されました。チェックポイントをオフにするか、<settingsLink>チェックポイント設定</settingsLink>で待機時間を延長できます。"
+		"init_checkpoint_fail_long_time": "チェックポイントの初期化が {{timeout}} 秒以上かかったため、このタスクではチェックポイントが無効化されました。チェックポイントをオフにするか、<settingsLink>チェックポイント設定</settingsLink>で待機時間を延長できます。",
+		"attempt_completion_tool_failed": "前回のツール呼び出しがこのターンで失敗したため、attempt_completionを実行できません。完了を試みる前にツールの失敗に対処してください。"
 	}
 }

webview-ui/src/i18n/locales/ja/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "モデル開始スラッシュコマンドを有効にする",
 			"description": "有効にすると、Rooがワークフローを実行するためにあなたのスラッシュコマンドを実行できます。"
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "並列ツール呼び出し",
+			"description": "有効にすると、ネイティブプロトコルは単一のアシスタントメッセージターンで複数のツールを実行できます。"
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/ko/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "{{timeout}}초 동안 체크포인트 초기화를 기다렸어. 체크포인트 기능이 필요 없다면 <settingsLink>체크포인트 설정</settingsLink>에서 꺼 줘.",
-		"init_checkpoint_fail_long_time": "체크포인트 초기화가 {{timeout}}초 이상 걸려서 이 작업에 대해 체크포인트가 꺼졌어. 체크포인트를 끄거나 <settingsLink>체크포인트 설정</settingsLink>에서 대기 시간을 늘릴 수 있어."
+		"init_checkpoint_fail_long_time": "체크포인트 초기화가 {{timeout}}초 이상 걸려서 이 작업에 대해 체크포인트가 꺼졌어. 체크포인트를 끄거나 <settingsLink>체크포인트 설정</settingsLink>에서 대기 시간을 늘릴 수 있어.",
+		"attempt_completion_tool_failed": "이전 도구 호출이 이 턴에서 실패했기 때문에 attempt_completion을 실행할 수 없습니다. 완료를 시도하기 전에 도구 실패를 해결하세요."
 	}
 }

webview-ui/src/i18n/locales/ko/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "모델 시작 슬래시 명령 활성화",
 			"description": "활성화되면 Roo가 워크플로를 실행하기 위해 슬래시 명령을 실행할 수 있습니다."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "병렬 도구 호출",
+			"description": "활성화되면 네이티브 프로토콜이 단일 어시스턴트 메시지 턴에서 여러 도구를 실행할 수 있습니다."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/nl/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Je hebt {{timeout}} seconden gewacht op de initialisatie van de checkpoint. Als je deze functie niet nodig hebt, schakel hem dan uit in de <settingsLink>checkpoint-instellingen</settingsLink>.",
-		"init_checkpoint_fail_long_time": "De initialisatie van de checkpoint duurde meer dan {{timeout}} seconden, dus checkpoints zijn uitgeschakeld voor deze taak. Je kunt checkpoints uitschakelen of de wachttijd in de <settingsLink>checkpoint-instellingen</settingsLink> verhogen."
+		"init_checkpoint_fail_long_time": "De initialisatie van de checkpoint duurde meer dan {{timeout}} seconden, dus checkpoints zijn uitgeschakeld voor deze taak. Je kunt checkpoints uitschakelen of de wachttijd in de <settingsLink>checkpoint-instellingen</settingsLink> verhogen.",
+		"attempt_completion_tool_failed": "Je kunt attempt_completion niet uitvoeren omdat een eerdere tool-aanroep in deze beurt is mislukt. Los het tool-probleem op voordat je probeert te voltooien."
 	}
 }

webview-ui/src/i18n/locales/nl/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Model-geïnitieerde slash-commando's inschakelen",
 			"description": "Wanneer ingeschakeld, kan Roo je slash-commando's uitvoeren om workflows uit te voeren."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Parallelle tool-aanroepen",
+			"description": "Wanneer ingeschakeld, kan het native protocol meerdere tools uitvoeren in één enkele assistent-berichtbeurt."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/pl/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Czekałeś {{timeout}} sekund na inicjalizację punktu kontrolnego. Jeśli nie potrzebujesz tej funkcji, wyłącz ją w <settingsLink>ustawieniach punktu kontrolnego</settingsLink>.",
-		"init_checkpoint_fail_long_time": "Inicjalizacja punktu kontrolnego trwała ponad {{timeout}} sekund, więc punkty kontrolne zostały wyłączone dla tego zadania. Możesz wyłączyć punkty kontrolne lub wydłużyć czas oczekiwania w <settingsLink>ustawieniach punktu kontrolnego</settingsLink>."
+		"init_checkpoint_fail_long_time": "Inicjalizacja punktu kontrolnego trwała ponad {{timeout}} sekund, więc punkty kontrolne zostały wyłączone dla tego zadania. Możesz wyłączyć punkty kontrolne lub wydłużyć czas oczekiwania w <settingsLink>ustawieniach punktu kontrolnego</settingsLink>.",
+		"attempt_completion_tool_failed": "Nie można wykonać attempt_completion, ponieważ poprzednie wywołanie narzędzia nie powiodło się w tym cyklu. Rozwiąż błąd narzędzia przed próbą zakończenia."
 	}
 }

webview-ui/src/i18n/locales/pl/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Włącz polecenia slash inicjowane przez model",
 			"description": "Gdy włączone, Roo może uruchamiać twoje polecenia slash w celu wykonywania przepływów pracy."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Równoległe wywołania narzędzi",
+			"description": "Po włączeniu protokół natywny może wykonywać wiele narzędzi w jednej turze wiadomości asystenta."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/pt-BR/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Você esperou {{timeout}} segundos para inicializar o checkpoint. Se não precisa dessa função, desative nas <settingsLink>configurações do checkpoint</settingsLink>.",
-		"init_checkpoint_fail_long_time": "A inicialização do checkpoint levou mais de {{timeout}} segundos, então os checkpoints foram desativados para esta tarefa. Você pode desativar os checkpoints ou aumentar o tempo de espera nas <settingsLink>configurações do checkpoint</settingsLink>."
+		"init_checkpoint_fail_long_time": "A inicialização do checkpoint levou mais de {{timeout}} segundos, então os checkpoints foram desativados para esta tarefa. Você pode desativar os checkpoints ou aumentar o tempo de espera nas <settingsLink>configurações do checkpoint</settingsLink>.",
+		"attempt_completion_tool_failed": "Não é possível executar attempt_completion porque uma chamada de ferramenta anterior falhou neste turno. Por favor, resolva a falha da ferramenta antes de tentar concluir."
 	}
 }

webview-ui/src/i18n/locales/pt-BR/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Ativar comandos slash iniciados pelo modelo",
 			"description": "Quando ativado, Roo pode executar seus comandos slash para executar fluxos de trabalho."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Chamadas paralelas de ferramentas",
+			"description": "Quando habilitado, o protocolo nativo pode executar múltiplas ferramentas em um único turno de mensagem do assistente."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/ru/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Ожидание инициализации контрольной точки заняло {{timeout}} секунд. Если тебе не нужна эта функция, отключи её в <settingsLink>настройках контрольных точек</settingsLink>.",
-		"init_checkpoint_fail_long_time": "Инициализация контрольной точки заняла более {{timeout}} секунд, поэтому контрольные точки отключены для этой задачи. Ты можешь отключить контрольные точки или увеличить время ожидания в <settingsLink>настройках контрольных точек</settingsLink>."
+		"init_checkpoint_fail_long_time": "Инициализация контрольной точки заняла более {{timeout}} секунд, поэтому контрольные точки отключены для этой задачи. Ты можешь отключить контрольные точки или увеличить время ожидания в <settingsLink>настройках контрольных точек</settingsLink>.",
+		"attempt_completion_tool_failed": "Невозможно выполнить attempt_completion, потому что предыдущий вызов инструмента не удался в этом повороте. Пожалуйста, устрани сбой инструмента перед попыткой завершения."
 	}
 }

webview-ui/src/i18n/locales/ru/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Включить слэш-команды, инициированные моделью",
 			"description": "Когда включено, Roo может выполнять ваши слэш-команды для выполнения рабочих процессов."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Параллельные вызовы инструментов",
+			"description": "При включении нативный протокол может выполнять несколько инструментов в одном ходе сообщения ассистента."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/tr/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "{{timeout}} saniye boyunca kontrol noktası başlatılması beklendi. Bu özelliğe ihtiyacın yoksa <settingsLink>kontrol noktası ayarlarından</settingsLink> kapatabilirsin.",
-		"init_checkpoint_fail_long_time": "Kontrol noktası başlatılması {{timeout}} saniyeden fazla sürdü, bu yüzden bu görev için kontrol noktaları devre dışı bırakıldı. Kontrol noktalarını kapatabilir veya <settingsLink>kontrol noktası ayarlarından</settingsLink> bekleme süresini artırabilirsin."
+		"init_checkpoint_fail_long_time": "Kontrol noktası başlatılması {{timeout}} saniyeden fazla sürdü, bu yüzden bu görev için kontrol noktaları devre dışı bırakıldı. Kontrol noktalarını kapatabilir veya <settingsLink>kontrol noktası ayarlarından</settingsLink> bekleme süresini artırabilirsin.",
+		"attempt_completion_tool_failed": "attempt_completion çalıştırılamıyor çünkü bu turda önceki bir araç çağrısı başarısız oldu. Lütfen tamamlamayı denemeden önce araç hatasını giderin."
 	}
 }

webview-ui/src/i18n/locales/tr/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Model tarafından başlatılan slash komutlarını etkinleştir",
 			"description": "Etkinleştirildiğinde, Roo iş akışlarını yürütmek için slash komutlarınızı çalıştırabilir."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Paralel araç çağrıları",
+			"description": "Etkinleştirildiğinde, yerel protokol tek bir asistan mesaj turunda birden fazla araç yürütebilir."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/vi/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "Bạn đã chờ {{timeout}} giây để khởi tạo điểm kiểm tra. Nếu không cần chức năng này, hãy tắt nó trong <settingsLink>cài đặt điểm kiểm tra</settingsLink>.",
-		"init_checkpoint_fail_long_time": "Khởi tạo điểm kiểm tra mất hơn {{timeout}} giây, vì vậy các điểm kiểm tra đã bị vô hiệu hóa cho tác vụ này. Bạn có thể tắt các điểm kiểm tra hoặc tăng thời gian chờ trong <settingsLink>cài đặt điểm kiểm tra</settingsLink>."
+		"init_checkpoint_fail_long_time": "Khởi tạo điểm kiểm tra mất hơn {{timeout}} giây, vì vậy các điểm kiểm tra đã bị vô hiệu hóa cho tác vụ này. Bạn có thể tắt các điểm kiểm tra hoặc tăng thời gian chờ trong <settingsLink>cài đặt điểm kiểm tra</settingsLink>.",
+		"attempt_completion_tool_failed": "Không thể thực thi attempt_completion vì một lệnh gọi công cụ trước đó đã thất bại trong lượt này. Vui lòng giải quyết lỗi công cụ trước khi cố gắng hoàn thành."
 	}
 }

webview-ui/src/i18n/locales/vi/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "Bật lệnh slash do mô hình khởi tạo",
 			"description": "Khi được bật, Roo có thể chạy các lệnh slash của bạn để thực hiện các quy trình làm việc."
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "Lệnh gọi công cụ song song",
+			"description": "Khi được bật, giao thức native có thể thực thi nhiều công cụ trong một lượt tin nhắn của trợ lý."
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/zh-CN/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "初始化存档点已等待 {{timeout}} 秒。如果你不需要存档点功能，请在<settingsLink>存档点设置</settingsLink>中关闭。",
-		"init_checkpoint_fail_long_time": "存档点初始化已超过 {{timeout}} 秒，因此本任务已禁用存档点。你可以关闭存档点或在<settingsLink>存档点设置</settingsLink>中延长等待时间。"
+		"init_checkpoint_fail_long_time": "存档点初始化已超过 {{timeout}} 秒，因此本任务已禁用存档点。你可以关闭存档点或在<settingsLink>存档点设置</settingsLink>中延长等待时间。",
+		"attempt_completion_tool_failed": "无法执行 attempt_completion，因为本轮中先前的工具调用失败了。请在尝试完成前解决工具失败问题。"
 	}
 }

webview-ui/src/i18n/locales/zh-CN/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "启用模型发起的斜杠命令",
 			"description": "启用后 Roo 可运行斜杠命令执行工作流程。"
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "并行工具调用",
+			"description": "启用后，原生协议可在单个助手消息轮次中执行多个工具。"
 		}
 	},
 	"promptCaching": {

webview-ui/src/i18n/locales/zh-TW/common.json

@@ -98,6 +98,7 @@
 	},
 	"errors": {
 		"wait_checkpoint_long_time": "初始化存檔點已等待 {{timeout}} 秒。如果你不需要存檔點功能，請在<settingsLink>存檔點設定</settingsLink>中關閉。",
-		"init_checkpoint_fail_long_time": "存檔點初始化已超過 {{timeout}} 秒，因此此工作已停用存檔點。你可以關閉存檔點或在<settingsLink>存檔點設定</settingsLink>中延長等待時間。"
+		"init_checkpoint_fail_long_time": "存檔點初始化已超過 {{timeout}} 秒，因此此工作已停用存檔點。你可以關閉存檔點或在<settingsLink>存檔點設定</settingsLink>中延長等待時間。",
+		"attempt_completion_tool_failed": "無法執行 attempt_completion，因為本輪中先前的工具呼叫失敗了。請在嘗試完成前解決工具失敗問題。"
 	}
 }

webview-ui/src/i18n/locales/zh-TW/settings.json

@@ -810,6 +810,10 @@
 		"RUN_SLASH_COMMAND": {
 			"name": "啟用模型啟動的斜線命令",
 			"description": "啟用時，Roo 可以執行您的斜線命令來執行工作流程。"
+		},
+		"MULTIPLE_NATIVE_TOOL_CALLS": {
+			"name": "並行工具呼叫",
+			"description": "啟用後，原生協定可在單個助理訊息輪次中執行多個工具。"
 		}
 	},
 	"promptCaching": {