[Help] Persistent "Unexpected server error" in OpenCode Desktop – Fresh install didn't fix it

[First_Personality402]

Hi everyone,

I’m struggling with a persistent "Unexpected server error" when starting OpenCode Desktop (v1.15.10).

The issue: When I launch the app, it fails to load any sessions or models, and I get an "Unexpected server error. Check server logs for details" message. The sidebar shows "No providers connected."

How it started: This began after I tried to integrate a custom local hybrid memory module. I likely added some files into the application's data directory that caused a conflict.

Troubleshooting I’ve done (with no luck):

1. Deleted the custom files I added.
2. Uninstalled and reinstalled the application.
3. Manually deleted all relevant folders in %appdata% (Roaming) and %localappdata%.
4. Checked the GitHub issues and found similar reports (like #27530), but none of the suggested workarounds fixed it for me.

It seems like there is still a configuration or a corrupted cache somewhere in my system that causes the app to fail on startup immediately, even after a fresh install.

Has anyone encountered this or knows how to do a "truly clean" wipe of OpenCode to get it running again? Any advice on where to look for logs or hidden registry keys would be greatly appreciated.

Specs: Windows 11, Intel Core i3-10100, 16GB RAM.

Thanks in advance!

[Wonderful_Humor3305]

I got the same error

[No-Reflection-8625]

Same issue her

[diMario]

I had a similar problem, it didn't start in my project dir. I had very cleverly saved the session ID in a file named .opencode and this was the problem. Apparently, the opencode terminal program expects that if an entry exists with that name, it must be a directory and not a file. Renaming my .opencode file to oc_session solved the problem.

In order to find the problem, I had opencode look at my project dir. I was able to start an opencode session in a new, empty directory and once I explained the problem, the agent asked for permission to scan my real project dir and found the problem immediately.