Desktop crashes on restart: "Notification server not found: wsl:Ubuntu" #37171

Activity

1. github-actions

   assigned

   Hona

   on Jul 15, 2026
2. github-actions commented on Jul 15, 2026

   

   github-actionsBot

   on Jul 15, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • OpenCode version: not provided (required)
   • Operating System: not provided (required)
   • Steps to reproduce: not provided — please describe what you were doing when the crash occurred (e.g. restarting the desktop app with a WSL server configured)
   • Terminal: not provided

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

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

   • OpenCode Desktop v1.17.14 can get stuck in an infinite startup crash loop with: Error: Notification server not found: http://[server-ip]:4096 #35686: Same "Notification server not found" crash on Desktop startup — identical error and stack trace, triggered by a stale/missing server key in persisted state

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   and removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jul 15, 2026
4. github-actions commented on Jul 15, 2026

   

   github-actionsBot

   on Jul 15, 2026 – with GitHub Actions

   Contributor

   More actions

   Thank you for updating the issue! All the required information is now present — the error message, steps to reproduce, OpenCode version, OS, and terminal details are all filled in. The compliance flag has been removed. We'll take a look!
5. Vidar-50rr commented on Jul 15, 2026

   

   Vidar-50rr

   on Jul 15, 2026

   More actions

   Same issue for me

   Error: Notification server not found: wsl:Ubuntu
       at ensure (oc://renderer/assets/main-BM2W0EK3.js:86341:24)
       at selected (oc://renderer/assets/main-BM2W0EK3.js:86373:28)
       at Object.ready (oc://renderer/assets/main-BM2W0EK3.js:86375:20)
       at Object.fn (oc://renderer/assets/main-BM2W0EK3.js:159881:23)
       at runComputation (oc://renderer/assets/main-BM2W0EK3.js:487:22)
       at updateComputation (oc://renderer/assets/main-BM2W0EK3.js:470:3)
       at runTop (oc://renderer/assets/main-BM2W0EK3.js:566:7)
       at runUserEffects (oc://renderer/assets/main-BM2W0EK3.js:660:39)
       at oc://renderer/assets/main-BM2W0EK3.js:634:35
       at runUpdates (oc://renderer/assets/main-BM2W0EK3.js:583:17)
       at completeUpdates (oc://renderer/assets/main-BM2W0EK3.js:634:18)
       at runUpdates (oc://renderer/assets/main-BM2W0EK3.js:584:5)
       at completeLoad (oc://renderer/assets/main-BM2W0EK3.js:167:5)
       at loadEnd (oc://renderer/assets/main-BM2W0EK3.js:162:14)
       at oc://renderer/assets/main-BM2W0EK3.js:232:28
   

   👍React with 👍2Reacted by BadLemon and Dave, Yu Jun Tham
6. kxt116

   marked Fatal renderer error on startup when the last-active URL is a WSL session #37224 as a duplicate of this issue on Jul 16, 2026
7. BadLemon5267 commented on Jul 17, 2026

   

   BadLemon5267

   on Jul 17, 2026

   More actions

   The same as version 1.18.3

   I'm working on v1.18.2, set the server WSL to default, then update and reboot.
   Start up and show the error as follows:

   Error: Notification server not found: wsl:Ubuntu
   at ensure (oc://renderer/assets/main-hem2imez.js:86345:24)
   at selected (oc://renderer/assets/main-hem2imez.js:86377:28)
   at Object.ready (oc://renderer/assets/main-hem2imez.js:86379:20)
   at Object.fn (oc://renderer/assets/main-hem2imez.js:159925:23)
   at runComputation (oc://renderer/assets/main-hem2imez.js:487:22)
   at updateComputation (oc://renderer/assets/main-hem2imez.js:470:3)
   at runTop (oc://renderer/assets/main-hem2imez.js:566:7)
   at runUserEffects (oc://renderer/assets/main-hem2imez.js:660:39)
   at oc://renderer/assets/main-hem2imez.js:634:35
   at runUpdates (oc://renderer/assets/main-hem2imez.js:583:17)
   at completeUpdates (oc://renderer/assets/main-hem2imez.js:634:18)
   at runUpdates (oc://renderer/assets/main-hem2imez.js:584:5)
   at completeLoad (oc://renderer/assets/main-hem2imez.js:167:5)
   at loadEnd (oc://renderer/assets/main-hem2imez.js:162:14)
   at oc://renderer/assets/main-hem2imez.js:232:28

   Here are exported logs.
   opencode-debug-20260717T032538.zip

   👍React with 👍1Reacted by Dave, Yu Jun Tham
8. huoyujia081 commented on Jul 17, 2026

   

   huoyujia081

   on Jul 17, 2026

   Last edited by huoyujia081

   More actions

   My current temporary workaround is:

   1. Delete the opencode.settings file in the %appdata%\ai.opencode.desktop directory
   2. Restart OpenCode Desktop on Windows
   3. Add a WSL server and set it as the default. This step is very important; otherwise, you'll have to delete opencode.settings again before it can start.
9. BadLemon5267 commented on Jul 17, 2026

   

   BadLemon5267

   on Jul 17, 2026

   Last edited by BadLemon5267

   More actions

   @huoyujia081 I tried deleting the opencode.settings file and restarting OpenCode Desktop, but it still shows the error: Notification server not found: wsl:Ubuntu. The new opencode.settings file doesn't even contain a WSL server entry.

   I delete %appdata%\ai.opencode.desktop directory and reinstall OpenCode Desktop, it works well now.

   I've been using it for a while, but it still throws the same error after a restart.😮
10. Aziteee commented on Jul 17, 2026

    

    Aziteee

    on Jul 17, 2026

    More actions

    Same issue here. I hope the app to still start up even if one of the servers is down.
11. fermumen commented on Jul 20, 2026

    

    fermumen

    on Jul 20, 2026

    More actions

    Additional confirmed repro on OpenCode Desktop 1.18.3 (Windows 11 + WSL2, distro Ubuntu-26.04).

    This was unrelated to plugins. Desktop persisted:

    {
      "wslServers": { "servers": [{ "id": "wsl:Ubuntu-26.04", "distro": "Ubuntu-26.04" }] },
      "defaultServerUrl": "wsl:Ubuntu-26.04"
    }

    in %APPDATA%\ai.opencode.desktop\opencode.settings.

    The exported debug logs show a startup race:

    • 12:23:39.683 WSL sidecar starting
    • 12:23:40.362 renderer fatal: Notification server not found: wsl:Ubuntu-26.04
    • 12:23:41.365 WSL sidecar ready

    So the renderer selects the configured default WSL server about one second before it is registered as ready. Clearing only defaultServerUrl while keeping the WSL server entry let the app start using the local sidecar.

    Suggested fix: defer/default-route notification-server selection until the selected sidecar is available, rather than calling ensure() fatally during initialization.
12. opencode-agent commented on Jul 20, 2026

    

    opencode-agentBot

    on Jul 20, 2026 – with OpenCode Agent

    Contributor

    More actions

    Fixed by #37890.
13. opencode-agent

    closed this as completedon Jul 20, 2026