desktop: recurring Session-not-found modal for session IDs that never existed (v2.0.32, Windows) #57026

Activity

1. opencode-agent commented on Oct 19, 2026

   

   opencode-agentBot

   on Oct 19, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report and logs. I reproduced what looks like the cause.

   The desktop app can't run in our sandbox, so I tested the client data layer it uses (createData in packages/client) against opencode serve 2.0.32:

   1. Connect the client to the server's event stream.
   2. Create a session with POST /api/session, then DELETE it right away. This is the same pattern your Feishu plugin uses for temporary sessions.
   3. The client receives the session.created event and fetches the new session with GET /api/session/<id>. By then the session is gone, so the request returns 404 Session not found: ses_…, and the error goes to the client's error handler. In the desktop app, that handler shows the "Request failed" toast you see. The server log has the same GET /api/session/ses_… 404 lines as yours.

   It still happens on the latest dev (ba06ff9). The script below reproduces it.

   So any session that is created and then deleted quickly can trigger the modal, whatever creates it. I couldn't tell which component creates sessions every ~20 minutes on your machine, but your guess about short-lived sessions matches what I saw.

   Related: #48012 (session-not-found errors are only detected in one shape) and #51940 (missing sessions are not handled when deleting).

   Reproduction script (repro-57026.ts)

   // Reproduction for #57026: the shared client data layer (used by the desktop app with an onError that
   // shows the "Request failed" toast) reacts to `session.created` by GET /api/session/<id>. If the session
   // is deleted right after creation (e.g. a plugin making a temporary session), that GET 404s and onError fires.
   // Usage: OC_URL=http://127.0.0.1:45278 OC_PASSWORD=... bun run repro-57026.ts   (from packages/client)
   import { createRoot } from "solid-js"
   import { OpenCode, type OpenCodeEvent } from "./src/promise/index.ts"
   import { createClientConnection, createData } from "./src/solid/index.ts"
   
   const url = process.env.OC_URL ?? "http://127.0.0.1:45278"
   const headers: Record<string, string> = process.env.OC_PASSWORD
     ? { authorization: "Basic " + Buffer.from(`opencode:${process.env.OC_PASSWORD}`).toString("base64") }
     : {}
   const api = OpenCode.make({ baseUrl: url, headers })
   const errors: unknown[] = []
   
   createRoot(() => {
     const handlers = new Map<string, Set<(e: any) => void>>()
     const all = new Set<(e: any) => void>()
     const connection = createClientConnection(api, {
       onEvent(event: OpenCodeEvent) {
         handlers.get(event.type)?.forEach((h) => h(event))
         all.forEach((h) => h({ name: event.type, details: event }))
       },
     })
     createData({
       api: () => api,
       directory: process.cwd(),
       connection,
       event: {
         on: (type: string, h: any) => (handlers.get(type) ?? handlers.set(type, new Set()).get(type)!).add(h) && (() => handlers.get(type)!.delete(h)),
         listen: (h: any) => (all.add(h), () => all.delete(h)),
       } as any,
       // Same hook the desktop app uses to show the "Request failed" toast.
       onError(error) {
         errors.push(error)
         console.log("onError (desktop would show 'Request failed' modal):", (error as any)?.message ?? error)
       },
     })
     ;(async () => {
       while (connection.status() !== "connected") await Bun.sleep(100)
       await Bun.sleep(500)
       // Temporary session: create, then delete straight away (like the plugin pattern in the report).
       const created = await fetch(`${url}/api/session`, {
         method: "POST",
         headers: { ...headers, "content-type": "application/json" },
         body: JSON.stringify({ location: { directory: process.cwd() } }),
       })
       const body: any = await created.json()
       const id = body.id ?? body.sessionID ?? body.data?.id
       console.log("created", created.status, id)
       const del = await fetch(`${url}/api/session/${id}`, { method: "DELETE", headers })
       console.log("deleted", del.status)
       await Bun.sleep(3000)
       console.log(errors.length ? `REPRODUCED: ${errors.length} onError call(s)` : "NOT reproduced: no onError")
       process.exit(errors.length ? 1 : 0)
     })()
   })

   Run it: bun repro-57026.ts
2. opencode-agent

   added

   reproduced

   on Oct 19, 2026
3. zr988888 commented on Oct 30, 2026

   

   zr988888

   on Oct 30, 2026

   More actions

   Cross-platform datapoint + one extra trigger, on macOS desktop 2.2.1 with a shared background opencode serve.

   • Same symptom: GET /api/session/<id> → canonical {"_tag":"SessionNotFoundError",...} for ids that don't exist server-side, recurring as a "Session not found" notification. Not Windows-only.
   • Additional trigger beyond the short-lived create/delete race: after bulk-deleting hundreds of test sessions, renderer references (drafts / closed tabs / layout) kept pointing at deleted ids and produced a burst of 404s.
   • Once a missing id is referenced, the deterministic 404 is retried indefinitely: one id was fetched 94 times over 43 minutes with +1/+2/+4/+8/+16/+30s then a fixed 30s cadence. I filed that retry-policy piece separately as client: a permanent 404 SessionNotFoundError is retried indefinitely with exponential backoff (one id: 94 requests / 43 min) #60413 — a defence independent of where the phantom id originates.
   • Restarting only the desktop renderer (not the service) dropped the 404 rate to 0 within a minute, consistent with the loop living in client/renderer state.
4. Hona

   closed this as completedin #60459on Oct 30, 2026