Repository navigation
Certain tool calling frequently fails and disconnects the chat #2519
Description
I've been getting a frequent error:
Error: The socket connection was closed unexpectedly. For more information, pass `verbose: true` in the second argument to fetch()
I think it's related to a failing tool call that fetches some info from the Web?
opencode — v0.6.6
macOS — v15.6.1
EDIT:
Potentially related to #2513
Same error string reported: #1692
Activity
github-actions commentedon Sep 9, 2025
This issue might be a duplicate of existing issues. Please check:
verbose: truein the second argument to fetch() #1692: Identical socket connection error messageFeel free to ignore if none of these address your specific case.
rekram1-node commentedon Sep 9, 2025
thx for raising
Durandle46 commentedon Oct 12, 2025
+1 on this issue.
Interestingly, it appears to have started working again once I deleted the.ideadirectory that GoLand had generated.My bad, I'd switched to Plan mode, which worked fine. Back to agent mode, same issue.
EDIT: The current task was trying to create an i18n file for the Lao language. I skipped that task, and the agent was able to continue. Any chance foreign characters were making the tools break?
rekram1-node commentedon Oct 12, 2025
if it is the socket error that is probably your provider dropping your connection unexpectedly that shouldnt have anytning to do with tools
at least nothing comes to mind ad to why thatd be
Durandle46 commentedon Oct 12, 2025
While I understand the technical reason for your point, the developer in me knows these things can often not be what they seem. What I know is when I made the agent skip whatever tooling it was trying to run and move to a different task, it immediately started working fine. That could still be the API/Provider being the issue, but could also be an internal issue triggering what looks like a timeout or connection drop. The agent came back to the whole Lao language thing and completed it eventually, just not when it originally tried to do it.
rekram1-node commentedon Oct 12, 2025
yeah i see, was this a toasted error for you or did you see it in the actual message history too
Durandle46 commentedon Oct 13, 2025
@rekram1-node
Toast and History
At the very least, it'd be useful to see the tool/request/details. Maybe a new
/whycommand that tells you about the last request, it's input, output, etc. Or a/retry-verbosethat re-runs the previous request but the results are verbose displayed.EDIT: I can confirm this is likely my provider. I managed to replicate the issue in a different IDE. However, I'd still like to have the ability to quickly enter a request into opencode CLI to see detailed info about the exact request that was dropped and stats around it.
rekram1-node commentedon Oct 13, 2025
thx for sharing
pjv commentedon Nov 21, 2025
Version 1.0.85 on macOS I'm seeing the same error happening but my provider is a lemonade server on my local LAN. still possible but lower likelihood that the local machine is dropping the connection. No other agents or web chats or other means of accessing the local provider are reporting any socket errors. Just opencode.
here's a fresh
/initin a new session in a test project:Since upgrading to 1.0.85 it looks to me like every tool call results in the same socket connection closed error. I know that i upgraded from 1.0.65 to 1.0.85, but unfortunately I cannot recall whether I was getting successful tool calls with 1.0.65 or if the last time I successfully used opencode was with an even earlier version than that. You guys are plowing through the version numbers pretty fast 😄 .
All I see in the log associated with the above is this:
Is there somewhere I can dig to try to debug this?
rekram1-node commentedon Nov 21, 2025
Maybe try
opencode run <prompt> --print-logsand try to get outputs?can also try running opencode yourself we should add some way to get fetch call logs or something
pjv commentedon Nov 22, 2025
@rekram1-node I've updated to opencode 1.0.98 and still seeing the same tool-calling socket error. Here is the result of your print-logs suggestion. I'm not seeing anything in here that seems helpful to my eyes. You?
rekram1-node commentedon Nov 23, 2025
alr ill look into it
rekram1-node commentedon Nov 24, 2025
@pjv that error is coming from your provider,
ECONNRESETmeans the server cutoff opencodes connectionpjv commentedon Nov 24, 2025
@rekram1-node I get that that's what the error means. What I don't get is why the provider only cuts off opencode. I use the same provider with other agents and front ends that also use tool-calling like goose, zed, openwebui, and none of them throw any such error or get interrupted. only opencode.
rekram1-node commentedon Nov 24, 2025
Can you share your opencode.json? Looks like a custom provider right
pjv commentedon Nov 24, 2025
Yes, it's a local lemonade server running on a different host on my LAN: