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
{{ message }}
Repository navigation
[Windows] App crashes on startup; Skills fail to load after killing bun process (v1.2.27) #18176
Bug: Desktop App crashes on startup, Skill loading fails after killing bun process (Windows)
Describe the bug
When launching OpenCode Desktop on Windows 11, the application throws an exception
on startup. After manually killing the bun process via Task Manager, the UI
becomes responsive and displays content correctly — however, all Skills fail to load.
Environment
OpenCode Desktop Version
v1.2.27
OS
Windows 11
Installation method
Official Windows installer (.exe) from opencode.ai/download
Bun version
Latest
Node.js version
Latest
Steps to reproduce
Launch OpenCode Desktop (v1.2.27) via the installed shortcut
Application throws an exception / fails to start properly
Open Task Manager → find and kill the bun.exe process
OpenCode UI becomes responsive and displays session info normally
All Skills fail to load
Actual behavior
OpenCode throws an exception on startup
After killing bun.exe, the UI loads but Skills are unavailable (loading failure)
Expected behavior
OpenCode should start without exceptions
Skills should load successfully without manual process intervention
Additional context
No crash log is generated / visible
The workaround of killing bun restores UI functionality but breaks Skill support
Issue is consistently reproducible on this machine
I have searched existing issues and this does not appear to be a duplicate
Activity
github-actions commentedon Mar 19, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct from these, please add additional details (e.g., error messages, crash output) to help distinguish it.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.