Error: Notification server not found: http://localhost:4096

[Bilge]

Description

On app start, Error: Notification server not found: http://localhost:4096.

Error: Notification server not found: http://localhost:4096
    at Object.ensure [as ensureServerState] (oc://renderer/assets/main-hem2imez.js:86345:24)
    at Object.fn (oc://renderer/assets/main-hem2imez.js:105957:44)
    at runComputation (oc://renderer/assets/main-hem2imez.js:487:22)
    at updateComputation (oc://renderer/assets/main-hem2imez.js:470:3)
    at Object.readSignal (oc://renderer/assets/main-hem2imez.js:403:67)
    at get unread (oc://renderer/assets/main-hem2imez.js:106104:21)
    at get when (oc://renderer/assets/main-hem2imez.js:106012:23)
    at Object.fn (oc://renderer/assets/main-hem2imez.js:1131:49)
    at runComputation (oc://renderer/assets/main-hem2imez.js:487:22)
    at updateComputation (oc://renderer/assets/main-hem2imez.js:470:3)
    at createMemo (oc://renderer/assets/main-hem2imez.js:119:3)
    at Show (oc://renderer/assets/main-hem2imez.js:1131:26)
    at oc://renderer/assets/main-hem2imez.js:927:24
    at untrack (oc://renderer/assets/main-hem2imez.js:268:33)
    at createComponent (oc://renderer/assets/main-hem2imez.js:927:10)
    at oc://renderer/assets/main-hem2imez.js:106010:18
    at ProjectAvatar (oc://renderer/assets/main-hem2imez.js:106028:5)
    at oc://renderer/assets/main-hem2imez.js:927:24
    at untrack (oc://renderer/assets/main-hem2imez.js:273:12)
    at createComponent (oc://renderer/assets/main-hem2imez.js:927:10)
    at projectAvatar (oc://renderer/assets/main-hem2imez.js:106091:31)
    at get fallback (oc://renderer/assets/main-hem2imez.js:106112:14)
    at Object.fn (oc://renderer/assets/main-hem2imez.js:1145:18)
    at runComputation (oc://renderer/assets/main-hem2imez.js:487:22)
    at updateComputation (oc://renderer/assets/main-hem2imez.js:470:3)
    at createMemo (oc://renderer/assets/main-hem2imez.js:119:3)
    at Show (oc://renderer/assets/main-hem2imez.js:1135:10)
    at oc://renderer/assets/main-hem2imez.js:927:24
    at untrack (oc://renderer/assets/main-hem2imez.js:268:33)
    at createComponent (oc://renderer/assets/main-hem2imez.js:927:10)
    at SessionTabAvatar (oc://renderer/assets/main-hem2imez.js:106107:10)
    at oc://renderer/assets/main-hem2imez.js:927:24
    at untrack (oc://renderer/assets/main-hem2imez.js:268:33)
    at createComponent (oc://renderer/assets/main-hem2imez.js:927:10)
    at oc://renderer/assets/main-hem2imez.js:164350:20
    at HomeSessionLeading (oc://renderer/assets/main-hem2imez.js:164368:5)
    at oc://renderer/assets/main-hem2imez.js:927:24
    at untrack (oc://renderer/assets/main-hem2imez.js:268:33)
    at createComponent (oc://renderer/assets/main-hem2imez.js:927:10)
    at oc://renderer/assets/main-hem2imez.js:164677:20
    at HomeSessionRow (oc://renderer/assets/main-hem2imez.js:164746:5)
    at oc://renderer/assets/main-hem2imez.js:927:24
    at untrack (oc://renderer/assets/main-hem2imez.js:268:33)
    at createComponent (oc://renderer/assets/main-hem2imez.js:927:10)
    at children (oc://renderer/assets/main-hem2imez.js:163742:46)
    at mapper (oc://renderer/assets/main-hem2imez.js:867:14)
    at updateFn (oc://renderer/assets/main-hem2imez.js:71:39)
    at runUpdates (oc://renderer/assets/main-hem2imez.js:576:23)
    at createRoot (oc://renderer/assets/main-hem2imez.js:75:12)
    at oc://renderer/assets/main-hem2imez.js:813:24

Plugins

None

OpenCode version

1.18.3

Steps to reproduce

1. Open app

Screenshot and/or share link

Operating System

Windows 11

Terminal

Windows Terminal

[github-actions]

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

• Desktop crashes on restart: "Notification server not found: wsl:Ubuntu" #37171: Desktop crashes on restart with "Notification server not found" error (same error, similar context)
• 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: Desktop stuck in infinite startup crash loop with the same "Notification server not found: http://[server-ip]:4096" error

If your issue is the same, please add a thumbs-up reaction or a comment on the existing issue rather than opening a new one. This helps us track and prioritize fixes more effectively.

[ajpintos]

Confirming this is a real 1.18.3 regression. Same root cause on Linux, slightly different symptom (raw Failed to fetch instead of the wrapped "Notification server not found" message, because the fetch dies earlier in the SDK on Linux).

Repro on Linux Mint 22.3 (.deb install, x86_64):

App crashes on launch:

Algo salió mal — Ocurrió un error al cargar la aplicación.
TypeError: Failed to fetch
at fetch (oc://renderer/assets/main-D0r_FFql.js:181444:45)
at request (oc://renderer/assets/main-D0r_FFql.js:65791:24)

~/.config/ai.opencode.desktop/logs/<date>/renderer.log:

error Failed to load sessions TypeError: Failed to fetch (×16 in ~30ms)
error (renderer) fatal renderer error { url: 'oc://renderer/index.html', version: '1.18.3' }
error Failed to finish bootstrap instance TypeError: Failed to fetch (×4)

main.log reports the sidecar healthy on a dynamic port (e.g. 127.0.0.1:38067). But curl http://127.0.0.1:38067/global/health returns:

HTTP/1.1 401 Unauthorized
www-authenticate: Basic realm="Secure Area"
vary: Origin

The main process's own health check (checkHealth in out/main/index.js:2299-2309) sends Authorization: Basic opencode:<random-uuid> and gets 200. The renderer doesn't, so it gets 401 → browser rejects the CORS response → promise rejects as TypeError: Failed to fetch.

Root cause (traced through the bundled app.asar):

out/main/index.js:3720 — main process generates a random password per sidecar:

const password = randomUUID();
out/main/sidecar.js:25-31 — sidecar passes it to the server listener:
listener = await Server.listen({
  port: command.port,
  hostname: command.hostname,
  username: "opencode",
  password: command.password,
  cors: ["oc://renderer"]
});
out/main/sidecar.js:47-52 — also sets the env var the server reads:
Object.assign(process.env, {
  OPENCODE_SERVER_USERNAME: "opencode",
  OPENCODE_SERVER_PASSWORD: password,
  ...
});
The renderer's SDK never receives the password. Two problems in the bundle:
1. out/renderer/assets/main-D0r_FFql.js:66039 — the SDK is hardcoded to the legacy CLI port:
const client = createClient(createConfig({ baseUrl: "http://localhost:4096" }));
That URL doesn't match the sidecar's dynamic port — hence this issue's title.
2. out/preload/index.js — contextBridge.exposeInMainWorld("api", { ... }) exposes no IPC for the renderer to retrieve sidecar credentials. The SDK's beforeRequest (main-D0r_FFql.js:65757-65762) only attaches an Authorization header when opts.security is set, which createConfig doesn't set. So the renderer fires fetch() against the sidecar with no auth → 401 → promise rejects.
On Windows the failure is caught a bit later, wrapped by ensureServerState, and surfaced as Error: Notification server not found. On Linux it hits the raw request() SDK path first, so it surfaces as TypeError: Failed to fetch. Same code path, different layer of error wrapping.
Likely the same root cause as #37353 (white screens & send failures on Windows + WSL, also 1.18.3) — Failed to fetch cascading into session-load failure produces the same visible symptoms there. Both should be tracked together.
Workaround (verified, unblocks the app on Linux):
Patch out/main/sidecar.js inside resources/app.asar:
 listener = await Server.listen({
   port: command.port,
   hostname: command.hostname,
-  username: "opencode",
-  password: command.password,
+  username: "",
+  password: "",
   cors: ["oc://renderer"]
 });
 Object.assign(process.env, {
-  OPENCODE_SERVER_USERNAME: "opencode",
-  OPENCODE_SERVER_PASSWORD: password,
+  OPENCODE_SERVER_USERNAME: "",
+  OPENCODE_SERVER_PASSWORD: "",
   XDG_STATE_HOME: process.env.XDG_STATE_HOME ?? userDataPath
 });
Extract the asar, apply the diff, repack with @electron/asar. The sidecar then starts in the same unsecured mode the CLI uses when OPENCODE_SERVER_PASSWORD is unset, the renderer's unauthenticated fetch succeeds, and sessions/projects load normally. Reverting to 1.18.2 also works.
Suggested fix in the repo:
- Bridge sidecar credentials main → renderer: add getSidecarCredentials() (or similar) to the contextBridge in out/preload/index.js, send { url, username, password } via IPC after server ready, and have the SDK either inject them into createClient config or attach an Authorization request interceptor.
- Drop the hardcoded baseUrl: "http://localhost:4096" fallback in main-D0r_FFql.js:66039 — the desktop sidecar doesn't run on that port.
Happy to test a fix branch when one is up.

[opencode-agent]

Fixed by #37890.

[Bilge]

I just updated and have the same issue. Was the fix not included in the 1.18.4 release?

[ajpintos]

I just updated and have the same issue. Was the fix not included in the 1.18.4 release?

I no longer update without checking the Changelog... (and praying that the update doesn't break anything!!!). I think they should improve the QA processes... I believe it's better to have one update a week or every 15 days that WORKS WELL than almost daily updates that break everything, all the time...