xxxigm f9ffe0bc3f fix(desktop): resume stored session id on notification click ... Native notifications (approval / sudo / secret / clarify) are tagged with the gateway *runtime* session id — the key under which the session lives in the gateway's in-memory `_sessions` map and the id every event carries (`tui_gateway/server.py` `_emit(event, sid, ...)`). The chat route, however, is keyed by the *stored* session id (`stored_session_id`), which is a different value: a new chat gets its runtime id immediately but its stored id only once the first turn persists. `onFocusSession` navigated straight to `sessionRoute(<runtime id>)`, so clicking a notification (e.g. an approval prompt) sent the route-resume path a runtime id where it expects a stored id. `useRouteResume` then resumed it as a stored session -> REST `/api/sessions/<runtime id>` 404 "session not found", and the running session was navigated away, which the user experiences as the session being destroyed. Translate runtime -> stored before navigating via the existing `runtimeIdByStoredSessionId` map (new `storedSessionIdForNotification` helper), falling back to the id as-is when no mapping is known. The Approve/Reject notification button path is untouched: `approval.respond` is routed by the runtime id (`_sess()` -> `_sessions[session_id]`), so it must keep carrying the runtime id.		2026-06-19 17:50:35 +05:30
..
bootstrap-installer	fix(desktop): retry the self-update rebuild once so the app relaunches (#48122)	2026-06-17 19:33:27 -05:00
desktop	fix(desktop): resume stored session id on notification click	2026-06-19 17:50:35 +05:30
shared	fix(desktop): move tsconfig to es2023	2026-06-15 12:07:17 -04:00