Repository navigation
[Windows] OpenCode binary is compiled with Bun 1.3.5, causing LSP crashes/blocks despite system Bun 1.3.8 #11824
Description
Description
I am running OpenCode on Windows 11. Although I have upgraded my system Bun version to 1.3.8 (which fixes the known Windows segmentation faults), OpenCode still detects the runtime environment as Bun 1.3.5 and blocks/crashes when using LSP tools.
It appears the opencode-windows-x64 binary distributed in the npm/bun package is a standalone executable compiled/bundled with Bun 1.3.5. This prevents Windows users from using LSP features even if they have fixed the Bun version on their system.
Error Message:
Error: Error: LSP server cannot be started safely.
Analysis:
- System Bun version is 1.3.8 (bun --version).
- Installed OpenCode v1.1.48 via bun install -g opencode-ai.
- The executed binary (C:\Users....bun\bin\opencode.exe) seems to be locked to the Bun version it was built with (1.3.5).
- Bun 1.3.5 has critical bugs on Windows causing segmentation faults with LSP usage.
Request:
Please rebuild and release the Windows binary using Bun >= 1.3.6 (preferably 1.3.8) to resolve the segmentation fault issues and allow LSP to work on Windows.
Plugins
oh-my-opencode, opencode-antigravity-auth
OpenCode version
1.1.48
Steps to reproduce
- On Windows 11, install Bun v1.3.8 (powershell -c "irm bun.sh/install.ps1|iex").
- Install OpenCode: bun install -g opencode-ai (or via npm).
- Verify system bun is new: bun --version -> 1.3.8.
- Start OpenCode: opencode (or bunx opencode).
- Trigger any LSP action (e.g., lsp_diagnostics).
- Result: The action fails with the "Windows + Bun v1.3.5 detected" error, indicating the internal runtime is still old.
Screenshot and/or share link
No response
Operating System
windows 11
Terminal
power shell
Activity
github-actions commentedon Feb 2, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if these don't address your specific case.
Happy-DJ commentedon Feb 5, 2026
+1 每沟通一个问题就崩溃一次，受不了了。
EricSolshkov commentedon Feb 5, 2026
You may try asking opencode to build a local version according to the build instructions in this repo (somehow like bootstrap). Since you are using a LLM tool to work, why not asking it to make a local build to save you from known bun crushes? This operation could be done with ONLY LLM and some simple instructions.
After clone, you re-specify the dependency of bun from 1.3.5 to 1.3.6(minimum change), and rebuild the cli and desktop target, and replace the original executables in PATH.(Don't forget to backup them and your previous sessions.)
PS 1. Before build operations, you MAY need to deploy some dependencies of build tool chain such as Rust, node, Tauri, etc. Since I am using Windows10 + MSVC, Rust + NodeJs + Tauri works for me.
PS 2. Before build operations, you MAY specify the version code for target exactly identical to the opencode you are using now. Otherwise your previous sessions may not appear.
This works for me, however, it is not guaranteed to be stable and safe, I am doing this ONLY BECAUSE an urgent need for LSPs. I am AWARE of that unstable build may corrupt my previous sessions.
github-actions commentedon Apr 7, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.