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
Opencode was working perfectly fine before and now suddenly it cannot be used. I don't think I did anything other than type "opencode" in the terminal and type my message. Error is in the screenshot.
Thanks for the report! To work out what's going wrong, could you share:
The error message as text: please copy and paste it here. It's hard for us to search for an error that's only in a screenshot.
The provider and model you were using (for example a free OpenCode model, OpenCode Go, Anthropic or OpenAI), and whether you updated OpenCode just before it stopped working.
If you can, the last lines of ~/.local/share/opencode/log/opencode.log from around the failure. Please remove anything sensitive first.
Something you could try in the meantime: run opencode service stop, then start opencode again. That fixed a similar problem after the 2.2.4 update for another user.
You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know you're done.
These existing issues may be related, ordered from most to least likely. Please check whether one of them already covers your problem:
We haven't heard back, so I'm closing this for now. Without the error message as text and the provider and model you were using, we couldn't work out what was failing; we couldn't read the error from the screenshot.
If it's still happening, please reply here with the error text and those details (and the last lines of ~/.local/share/opencode/log/opencode.log if you can), and we'll take another look. You can also try opencode service stop, then start opencode again, or check whether #60724 or #60667 matches what you're seeing. Thanks!
Thanks for the report! This ECONNRESET: The socket connection was closed unexpectedly error is tracked in #60399, which covers the cause (networks dropping the TLS handshake) and has workarounds. Please follow that issue for updates and add your details there if the workarounds don't help.
Activity
opencodejr commentedon Oct 30, 2026
Thanks for the report! To work out what's going wrong, could you share:
~/.local/share/opencode/log/opencode.logfrom around the failure. Please remove anything sensitive first.Something you could try in the meantime: run
opencode service stop, then startopencodeagain. That fixed a similar problem after the 2.2.4 update for another user.You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know you're done.
These existing issues may be related, ordered from most to least likely. Please check whether one of them already covers your problem:
table session_inbox has no column named typeopencode service stopfixed itVariableVince commentedon Oct 30, 2026
@opencodejr it's the same error that's being reported here as well: #60742 (comment) and here #60700
FlyingMansion701 commentedon Oct 31, 2026
@opencodejr
I don't know exactly what in the log file to put so i just put a download link for it
opencodejr commentedon Nov 2, 2026
We haven't heard back, so I'm closing this for now. Without the error message as text and the provider and model you were using, we couldn't work out what was failing; we couldn't read the error from the screenshot.
If it's still happening, please reply here with the error text and those details (and the last lines of
~/.local/share/opencode/log/opencode.logif you can), and we'll take another look. You can also tryopencode service stop, then startopencodeagain, or check whether #60724 or #60667 matches what you're seeing. Thanks!neriousy commentedon Nov 4, 2026
Thanks for the report! This
ECONNRESET: The socket connection was closed unexpectedlyerror is tracked in #60399, which covers the cause (networks dropping the TLS handshake) and has workarounds. Please follow that issue for updates and add your details there if the workarounds don't help.Closing as a duplicate of #60399.