Opencode team throws opencode in trash bin: Where are normal "opencode-desktop-windows-x64.exe" builds which are Not Electron builds. becaue eveything is broken now.

[Zeal29]

Question

I was using v1.14.33 with the oh-my-openagent plugin, and things were working, and I was happy. But then I saw the update. I updated to v1.14.41, and what a huge pain in the ass it was. Things started breaking, and oh-my-openagent was not working properly, and I was getting pissed off. What happened? and eventually figure out that after v1.14.33, the OpenCode team stopped shipping normal desktop builds and instead called them "overweight." Electron builds as the desktop builds. What a shame. Why do you do that? oh-my-openagent is the most powerful plugin of opencode, and you didn't even test it?

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Opencode desktop(Windows) doen'st show oh-my-openagent #26123: Opencode desktop (Windows) doesn't show oh-my-openagent — same symptom, very recent
• Win Desktop can not use OMO plugin #26209: Win Desktop can not use OMO plugin — same symptom, very recent
• Desktop v1.14.39: Bun-target plugins fail to load (Node.js sidecar lacks Bun APIs) #25880: Desktop v1.14.39 Bun-target plugins fail to load (Node.js sidecar lacks Bun APIs) — likely the root cause
• v1.14.35 Desktop shows plugin loaded, but oh-my-openagent custom agents not visible in GUI (TUI works when launched from same exe) #25824: Desktop shows plugin loaded but oh-my-openagent custom agents not visible in GUI (v1.14.35)
• After update to v.14.37, in desktop app. Agent not showing up the plugin list. In CLI it is working fine. #25840: After update to v1.14.37, agents from plugin not showing in desktop app

The underlying cause appears to be the switch from a Bun to Node.js sidecar in v1.14.34+, which broke Bun-target plugins including oh-my-openagent. Please review these issues — your report may already be tracked there.

[dubujianghu]

希望尽快解决，谢谢

[kiyosunsun]

I was in the same situation as you, and then I uninstalled it directly, because I found that the new installation package path after the update was different from the original, resulting in two opencodes appearing on my computer, and the OMO plug-in I installed before could not be used

[Litmus505]

You can just uninstall the 1.14.41 and use C:\Users\xxx\AppData\Local\OpenCode\OpenCode.exe(v1.14.33) to workaround. v1.14.33 works fine with OMO.

[rekram1-node]

Automated: closing question issues.

GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.

• For help & questions: https://discord.gg/opencode
• Billing issues with Opencode Go / Zen: help@anoma.ly

If this is a bug or feature request, please open a new issue with the appropriate template.