[BUG] Can you please revert to XML tool selection ?

[torxeon]

Problem (one or two sentences)

I'm having trouble adapting to this newer ts format of tool calls. please, if possible, revert back to manually selecting XML tool under model advanced settings as in 3.36 versions

I don't know why you guys changed it, it was perfect. now i'll be stuck with older version praying you revert it back.

PS. not everyone is technical as you guys. so building my own custom made tools on ts is a daunting task that i really don't have time for.

Context (who is affected and when)

NA

Reproduction steps

NA

Expected result

NA

Actual result

NA

Variations tried (optional)

No response

App Version

3.37.1

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

Thank you for raising this issue. I want to clarify what changed and understand your concern better.

What Changed in 3.37

In version 3.37.1, PR #10281 deprecated the XML tool protocol selection UI. The change:

• Removed the "Tool Call Protocol" dropdown from the Model Settings
• Forces all new tasks to use the "native" tool calling protocol (which is the standard API mechanism for tool/function calling)
• Existing tasks that were started with XML protocol can still be resumed with XML

Note: The "native" protocol is not TypeScript. It refers to the standard tool/function calling mechanism provided by LLM APIs (like Claude's tool_use, OpenAI's function_calling, etc.). The XML protocol was an older approach where tool calls were serialized as XML text in the assistant's response.

Clarifying Questions

To better understand your use case and provide the right solution, could you please clarify:

1. What specific issue are you experiencing? Are you seeing different behavior in how Roo Code executes tools, or is it an issue with the visible output/format in the chat?

2. Which API provider and model are you using? This helps us understand if your model might have compatibility issues with native tool calling.

3. What do you mean by "ts format of tool calls"? If you are referring to something specific you're seeing in the output, could you share a screenshot or example?

4. Are you building custom tools/extensions? If so, could you describe your setup?

Please mention @roomote in your response with these details, and I'll be happy to help find a solution or propose an implementation plan.

[WeOneGuy]

agreed