Repository navigation
have error with tool call from 1.0.62 build ( current 1.0.65 still have this issue ) #4322
Description
Description
have problem with tool call on 1.0.65 - its also be on 1.0.62 issue
Thinking: <tool_call>edit
<arg_key>filePath</arg_key>
<arg_value> Project file </arg_value>
<arg_key>oldString</arg_key>
<arg_value> SearchResultRow(result: result) {
Task {
await Project file (to: result.id)
}
}</arg_value>
<arg_key>newString</arg_key>
<arg_value> SearchResultRow(result: result) {
Task {
await Project file(to: result.id)
}
}</arg_value>
</tool_call>
using Z.AI Coding Plan GLM 4.6
on v1.0.59 - rlease don't have this issue
OpenCode version
1.0.65
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
macOS 26.1 (25B78)
Terminal
Warp ( Ghostty have same issue )
Activity
github-actions commentedon Nov 14, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Nov 14, 2025
what is your problem with tool calling? Is rhe model failing to call tools correctly?
Wierzciu commentedon Nov 14, 2025
@rekram1-node Hi there!
I’m not using any custom tools, but I’m seeing this fragment:
Thinking: <tool_call>edit
<arg_key>filePath</arg_key>
<arg_value>Project file</arg_value>
<arg_key>oldString</arg_key>
<arg_value>SearchResultRow(result: result) {
Task {
await Project file (to: result.id)
}
}</arg_value>
<arg_key>newString</arg_key>
<arg_value>SearchResultRow(result: result) {
Task {
await Project file(to: result.id)
}
}</arg_value>
</tool_call>
After this, nothing happens — there’s no animation or indication that the model is working. It feels like the session just freezes or crash.
rekram1-node commentedon Nov 14, 2025
@Wierzciu so that's the model failing to call tools, it is sending back text instead of tool call parts and we render it as is. This happens typically with the OSS models sometimes.
It shouldn't be causing any freezes tho, I bet the model stops in place but you should be able to follow up and tell it to correct how it is calling tools.
This isn't really opencode's fault tho we could try to do an additional layer of tool call parsing (provider does it for us rn), generally you just have to correct the model with prompting