Repository navigation
[BUG] Issues with OpenCode: panic(thread 33600): invalid enum value #26496
Description
What version of Bun is running?
bun 1.3.7
What platform is your computer?
Command didn't work, 1.3.7
What steps can reproduce the bug?
open up opencode, type in a prompt hit enter.
What is the expected behavior?
it works, no issues.
What do you see instead?
Additional information
No response
Activity
Jarred-Sumner commentedon Jan 27, 2026
This is 1.3.5, please give it another go after they upgrade
fix(watcher): handle unknown file action codes in Windows watcher
github-actions commentedon Jan 27, 2026
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
mynameistito commentedon Jan 27, 2026
issues persist on 1.3.7
mynameistito commentedon Jan 27, 2026
It still says as 1.3.5
but I ran this straight after the crashing and it showed up as 1.3.7
Currently on W10 x64
mynameistito commentedon Jan 27, 2026
Hmm weirdly it seems to work in normal Terminal but not Warp lol
ArcherZX commentedon Jan 28, 2026
Troubleshooting Steps
Install the latest version of Bun by running: powershell -c "irm bun.sh/install.ps1 | iex"
Locate the new binary: Find bun.exe in the .bun/bin/ folder under your user directory.
Navigate to the target folder: Go to your Node installation directory: .../nodejs/node_modules/oh-my-opencode-windows-x64/bin/
Backup the original file: Rename the existing oh-my-opencode.exe to oh-my-opencode-old.exe.
Replace the engine: Copy the new bun.exe into this folder and rename it to oh-my-opencode.exe.
Verify: Run oh-my-opencode install. It should now execute successfully without the segmentation fault.
mynameistito commentedon Jan 28, 2026
My issues seemed to somewhat stop like it's slight happening still but less.
Also I am not running oh my OC
mynameistito commentedon Jan 28, 2026
Issue is back, weirdly only happens on Warp 😭
My bun v is 1.3.7 but I assume OpenCode is locking it to 1.3.5?
ivanosquis10 commentedon Feb 9, 2026
same error here, only happens on warp lol
Hona commentedon Mar 7, 2026
@ivanosquis10 do you have a crash log for warp?
e.g. I'd like on on latest bun 1.3.10 pls to help repro
sys(windows): don't panic on unnamed NTSTATUS in openDirAtWindowsNtPath