Plugin Crashes OpenCode

[DasOhmoff]

Hello and thank you for this nice plugin :)

Recently I installed the plugin on my windows 10 machine, and since then the plugin started crashing the whole OpenCode instance. I am not sure when exactly this happens, but I think it happens when a sound is played. What can I do about it?

Here is the crash report: https://bun.report/1.3.5/wa11e86cebmzGz+3/9/D_+4q0ekoq0e8xh+nBg4rovBw9vqvBkr45vB2115vB8w14vBirj5vBy004vB6xnjwB220ywBk+15vBy0x4vB67u4vB+7t4vBqu5lwBon005By7y05BA2Wpv33gR

Thank you for your help.

[mohak34]

Hey could you let me know about the windows version/build ? Also the plugin version and opencode version. Could you also share you opencode-notifier config and your opencode config ?

Windows version/build :

systeminfo | Select-String "OS Name","OS Version","System Type"

OpenCode version :

opencode --version

Plugin version (cached install) :

Get-Content "$env:USERPROFILE\.cache\opencode\node_modules\@mohak34\opencode-notifier\package.json" | Select-String '"version"'

Also could you let me know if this issue is solved when you disable the sounds from adding false in the config ?

[DasOhmoff]

Hey.

Windows version/build :

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
System Type:               x64-based PC
BIOS Version:              American Megatrends International, LLC. F35, 7/16/2025

OpenCode version : 1.1.56

Plugin version (cached install) : "version": "0.1.18",

OpenCode config:

{
  "$schema": "https://opencode.ai/config.json",
  "keybinds": {
    "input_line_home": "ctrl+a,home",
    "input_line_end": "ctrl+e,end",

    "input_buffer_home": "none",
    "input_buffer_end": "none",

    "messages_first": "ctrl+g",
    "messages_last": "ctrl+alt+g"
  },
  "plugin": ["@mohak34/opencode-notifier@latest"]
}

OpenNotifier Config: none

I also tested out the following config, it still crashes:

{
  "sound": false
}

Even without any config, I am not sure at what points it crashes. Sometimes it runs and plays notification sounds, and crashes eventually at another point.

Thanks again!

[shiquda]

Same issue on Windows 11.

OS Name:                       Microsoft Windows 11 Pro
OS Version:                    10.0.26200 N/A Build 26200
System Type:                   x64-based PC
BIOS Version:                  LENOVO LZCN44WW, 2025/12/17

Opencode version: 1.1.59, Plugin version: 0.1.18

Full OpenCode plugin list:

  "plugin": [
    "opencode-antigravity-auth@beta",
    "oh-my-opencode@latest",
    "@mohak34/opencode-notifier@latest"
  ]

Even without any config, I am not sure at what points it crashes. Sometimes it runs and plays notification sounds, and crashes eventually at another point.

The plugin behaves the same way on my machine.

Bun crash reporting link: https://bun.report/1.3.8/wa1b64edcbmzGz+3/8/DA2AA

[shiquda]

This appears to be an upstream issue with Bun:

oven-sh/bun#26026

And the crash happens a while after the notification pops up, with the program running normally in between.

[mohak34]

@DasOhmoff @shiquda There seems to be an issue with Bun and the embedded bun version in OpenCode. It seems to be affecting any child process spawning with either notifications or LSP's. There are multiple issues opened in Opencode repo regarding this.

For the time being, you could switch off the notifications in the config file and use the commands feature in the plugin to receive notifications. You could do it like this :

{
  "notification": false,
  "sound": true,
  "command": {
    "enabled": true,
    "path": "powershell.exe",
    "args": [
      "-Command",
      "$wshell = New-Object -ComObject Wscript.Shell; $wshell.Popup('{message}', 5, 'OpenCode - {event}', 0+64)"
    ],
    "minDuration": 5
  }
}

If you want more details about this you could check issue #24 for how you could customize it to you liking. Will be adding this to the README as well as an example for using commands.

[shiquda]

Hi @mohak34 thank you for your temporary solution! This seems to be working on my machine.

[DasOhmoff]

Yes, thanks @mohak34 :) I guess you can close this issue now if you like. Or keep it open until upstream is fixed