Desktop: white screens & send failures from corrupted global state JSON, stale session.path, dangling server refs (1.18.3, Windows + WSL) #37353

Activity

1. github-actions

   assigned

   Brendonovich

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

   

   github-actionsBot

   on Jul 16, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Error: Notification server not found: http://localhost:4096 #37331: Same "Notification server not found" error on app start — your issue identifies the root cause (dangling server reference after deletion), which likely explains the symptom reported there as well.
3. robertn702 commented on Jul 19, 2026

   

   robertn702

   on Jul 19, 2026

   More actions

   Another data point, this time on macOS (Desktop 1.18.3) — so not WSL-specific. Same failure family: opencode.global.dat + stale absolute paths.

   What happened here: a Superset worktree subfolder (/Users/robert/.superset/worktrees/540f8918-…/test-setup) was deleted out from under the app. The app kept it in the server key of opencode.global.dat:

   "projects": { "local": [
     { "worktree": "…/test-setup", "expanded": true },
     { "worktree": "/Users/robert/Documents/Default Project", "expanded": true }
   ]},
   "lastProject": { "local": "…/test-setup" }

   Symptoms:

   • Every launch: sidecar realpath(lastProject) inside Server.listen → PlatformError: NotFound … ENOENT; /api/reference?directory=<deleted> → HTTP 500.
   • Every send in the affected sessions: prompt_async failed with Cause([Die(PlatformError: NotFound: FileSystem.realPath (…))]) — and no error in the chat UI. The message appears to send; the session never responds.
   • Renderer console stays clean (only ResizeObserver noise). The failure is only visible in ~/.local/share/opencode/log/opencode.log and the app's Chromium netlog (…/T/ai.opencode.desktop.scoped_dir./event_file_.json`).
   • The UI derives the displayed project from the git root, so the dead worktree path is invisible — it looks like "the main project is broken", and selecting the main worktree doesn't help because new sessions were still being created against lastProject`.

   Strong +1 on the repair-path suggestions: in this state there is no in-app way to fix or even diagnose it — I had to inspect the netlog and sqlite DBs to find the binding. Boot-time validation of projects[].worktree / lastProject (drop-or-flag missing) plus an in-chat error when prompt_async dies would have made this a 30-second fix.
4. wkkxkc commented on Sep 13, 2026

   

   wkkxkc

   on Sep 13, 2026

   More actions

   I think I found another way to hit the corrupted global store problem described here.

   On the affected Windows machine, opencode.global.dat started with a UTF-8 BOM (EF BB BF). The rest of the file was valid JSON, but electron-store passes the decoded U+FEFF straight to JSON.parse, so the store could no longer be read.

   This was hard to notice because store-get catches the error and returns null, while store-set rejects. In my case the model visibility toggles worked until restart, and renderer.log showed the same SyntaxError for every write.

   Removing only the BOM fixed it. The existing values loaded again, and the next write rewrote the file without the BOM.

   I checked the current dev branch at 95daf906: store.ts still uses the default deserializer, and the store-get / store-set behavior is unchanged. I also couldn't find an existing report or PR for this specific BOM case.

   Would a small PR that strips a leading BOM during deserialization and adds a regression test be welcome? I can leave the broader backup/reset behavior for malformed JSON as a separate change.
5. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
6. thdxr

   closed this as not plannedon Oct 11, 2026