Session-not-found errors are only detected in the exact V1 shape, other wrappers are missed #48012

Activity

1. github-actions

   assigned

   Hona

   on Sep 8, 2026
2. github-actions commented on Sep 8, 2026

   

   github-actionsBot

   on Sep 8, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • tui: stale subagent sessions cause SessionNotFoundError unhandled rejection bursts #47516: stale subagent sessions cause SessionNotFoundError unhandled rejection bursts — overlapping symptom of SessionNotFoundError not being handled, possibly related to the same detection gap
   • References to a deleted session outlive it: address bar, recent-tab pointer and persisted handoff #47683: references to a deleted session outlive it (address bar, recent-tab pointer, persisted handoff) — same root symptom of UI not correctly treating a session as gone after deletion
   • Desktop renderer fatally crashes (404 NotFoundError) when lastProjectSession references a session missing from opencode.db #32473: Desktop renderer crashes with 404 NotFoundError when lastProjectSession references a session missing from opencode.db — another case where a not-found session isn't routed correctly

   If your issue is specifically about the isSessionNotFoundError / isLocalSessionNotFoundError detection functions missing non-V1 error shapes (plain string, NotFoundError object, etc.), it may be distinct from the above. Please cross-reference and close or link as appropriate.
3. CannonRS commented on Sep 8, 2026

   

   CannonRS

   on Sep 8, 2026

   Author

   More actions

   These related issues describe observable symptoms of a session going away (renderer crash on a stale lastProjectSession pointer, unhandled rejection bursts from stale subagent sessions, survivor references). This issue is narrower and distinct: it targets the two detection predicates (isSessionNotFoundError / isLocalSessionNotFoundError) that decide whether an incoming error is a not-found shape at all. Fixing the predicates makes all three symptom paths route correctly through the existing "session gone" handling instead of treating the error as generic.

   Cross-reference: the mQorva fork has a related fix for the survivor-reference path (#47683 / stale-session-references); this issue covers the shared predicate that both that fix and the crash/overlay paths depend on.
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed write-up!

   On current dev, the server converts a missing session into a tagged SessionNotFoundError ({ _tag: "SessionNotFoundError", sessionID, message }) in packages/server/src/handlers/session-error.ts, and isSessionNotFoundError in the app matches that shape. I couldn't find a v2 server path that returns name: "NotFoundError" with data.message; that looks like the v1 error format. To check whether there's a real gap, could you share:

   • The exact action and request that failed (for example rename, load or switch, and which endpoint it calls, if you know).
   • The raw error the app received: the response body and status from the network tab or the server logs, or the error value reaching isSessionNotFoundError.
   • The output of opencode --version for the server you were connected to, and how it was started (desktop app, opencode serve, etc.).

   You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
5. opencodejr

   added

   triaging

   on Oct 28, 2026
6. opencodejr

   closed this as not plannedon Oct 31, 2026
7. opencodejr commented on Oct 31, 2026

   

   opencodejrBot

   on Oct 31, 2026

   Contributor

   More actions

   Closing this for now, since we haven't heard back. To tell whether isSessionNotFoundError really misses a case, we'd need to see a v2 server send a session-not-found error in a shape the check doesn't recognise. The server code on dev always sends the tagged SessionNotFoundError, and the check matches that.

   If you see this happen, please comment here or open a new issue with:

   • the action or request that failed
   • the raw response body and status, or the error value the app received
   • your opencode --version

   We'll be happy to take another look. Thanks for reporting!