You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Qwen3 Coder on OpenCode Zen: Tool call metadata being printed to chat instead of actually being called #10855
But the first issue wasn't very clear and the second issue looks more like an issue around prompting the user to answer a question. My issue is just basic file edits are failing:
It's completely stuck here. Every time I try to re-prompt it to try again it fails in the same way.
I'm not sure if the issue is with the Qwen3 model or OpenCode Zen: Once I switching from "Qwen3 Coder on OpenCode Zen" to using "GLM 4.7 via OpenRouter" - the issue stopped occurring.
Yes, it happens with nemotron 3 nano too. I note that, if a tool call attempt is made with invalid parameters, then opencode tells the model that it made a mistake in the tool call, asks it to retry. I believe it should do the same if XML-style tool call attempts are detected.
Getting this with GLM-4.7 as well. I was on 1.1.28 previous, now on 1.1.48. What I suspect the issue was with continuing a conversation created with an old version. I haven't been able to repro the issue since creating a new conversation
Activity
github-actions commentedon Jan 27, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
bi-kai commentedon Jan 29, 2026
same issue, with GLM 4.7, this issue comes up quite frequently.
lee-b commentedon Jan 30, 2026
Yes, it happens with nemotron 3 nano too. I note that, if a tool call attempt is made with invalid parameters, then opencode tells the model that it made a mistake in the tool call, asks it to retry. I believe it should do the same if XML-style tool call attempts are detected.
Mattwmaster58 commentedon Feb 1, 2026
Getting this with GLM-4.7 as well. I was on 1.1.28 previous, now on 1.1.48. What I suspect the issue was with continuing a conversation created with an old version. I haven't been able to repro the issue since creating a new conversation
RawthiL commentedon Feb 3, 2026
any chance this is related to this vLLM issue? vllm-project/vllm#22975
I facing this when running a local instance of vLLM and Qwen3-30B and
qwen3_xmltool parset. The model just prints the xml of the tool call.github-actions commentedon Apr 5, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.