Broken XML auto fixing

[BHznJNs]

App Version

3.25.16

API Provider

OpenAI Compatible

Model Used

Qwen3-coder-480B

Roo Code Task Links (Optional)

https://app.roocode.com/share/d70b106a-17d9-4780-a356-917e96407980

🔁 Steps to Reproduce

For some LLM providers (like Targon), the model can not response with a right XML tool call sequence, but a broken sequence like:

read_file>
args>
<file>
<path>main.gopath>
</file>
args>
read_file>

Even with such a prompt:

Please reply with the XML sequence below：
\`\`\`
<read_file>
<args>
<file>
<path>main.go</path>
</file>
</args>
</read_file>
\`\`\`

Maybe we can config a small model to use it to fix the returned broken XML like:

Please try fix the broken XML sequence below:
\`\`\`
read_file>
args>
<file>
<path>main.gopath>
</file>
args>
read_file>
\`\`\`

We can have an extra config item for OpenAI Compatible mode, when the item is on, it will automatically detect if the response has a broken XML tool call, and use the small model to fix it.

💥 Outcome Summary

Expected tool calls successfully, but responses with a broken XML sequence like:

read_file>
args>
<file>
<path>main.gopath>
</file>
args>
read_file>

📄 Relevant Logs or Errors (Optional)

[BHznJNs]

I have created a repo https://github.com/BHznJNs/xml-patcher which is aimed to patch the wrong XML instructions, which can be a reference.

[NaccOll]

Does Qwen3-coder-480B on targon support tool calls? If so, you can try #6744 . Based on native tool calls, it avoids the problem of incorrect call format.

[daniel-lxs]

I wonder if this is a problem with the model/provider rather than a problem with our parser. If so, I would like to explore solutions that don't involve making our parser more complex to deal with edge cases like this one.