windows system opencode bug #10992

Activity

1. LoukasChen

   added

   bugSomething isn't workingSomething isn't working

   on Jan 28, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 28, 2026
3. github-actions

   added

   windows

   on Jan 28, 2026
4. github-actions commented on Jan 28, 2026

   

   github-actionsBot

   on Jan 28, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Bun has crashed #8785: Bun has crashed - Similar Windows Bun segmentation fault crash with KERNEL32.DLL
   • OpenCode crashed during LLM analysis of IndexedDB #10799: OpenCode crashed during LLM analysis of IndexedDB - Windows 11 Pro Bun v1.3.5 segmentation fault
   • TypeScript LSP crashes with Bun segmentation fault on Windows 11 #7318: TypeScript LSP crashes with Bun segmentation fault on Windows 11 - Similar Bun crash pattern
   • OpenCode crashes during use on Windows (garbled console output) #10414: OpenCode crashes during use on Windows (garbled console output) - Windows crash with console issues
   • Windows 11: desktop program starts with error #9074: Windows 11: desktop program starts with error - Windows 11 startup error

   These all appear to be related to Bun runtime crashes on Windows systems. Your issue might be covered by the investigation into these similar crashes.

   Feel free to ignore if your specific case differs from these.
5. kskyj commented on Mar 19, 2026

   

   kskyj

   on Mar 19, 2026

   More actions

   I’ve found the root cause of this issue!

   It seems to be triggered by the presence of a .env file in the directory where opencode is executed.

   Here is what I discovered:

   If the .env file is empty (0kb), it works fine.

   If the .env file has any content, the issue occurs.

   As a workaround, check if there is an existing .env file in your current working directory and try removing or emptying it.
6. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   windows

   on May 3, 2026
7. github-actions commented on Jul 6, 2026

   

   github-actionsBot

   on Jul 6, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as not plannedon Jul 6, 2026