[BUG] Closing and reopening Claude Desktop (Linux) forces Google re-login — app keeps running hidden in background

Environment

• OS: Ubuntu 24.04.4 LTS (Linux)
• Claude Desktop version: 1.30096.1 (Electron 42.7.0)
• Login method: Google OAuth (system browser)

Symptom

From my side, this looks like a plain close-and-reopen: I close the Claude
Desktop window, then later click the launcher icon to reopen it. Instead of
returning to my still-open session, the app forces a full re-login (redirect
to claude.ai Google OAuth in the system browser).

Root cause (confirmed from ~/.config/Claude/logs/main.log and ps)

Closing the window does not quit the app process. There is no tray icon
shown, and no before-quit / will-quit / window-all-closed lifecycle
event is ever logged — the process just keeps running hidden in the
background, still authenticated. I confirmed this directly: the main process
PID stayed the same and had a single continuous uptime spanning straight
through a disconnect event (it never restarted).

So what actually happens on "reopen" is:

1. The launcher starts a new process.
2. Electron's single-instance lock detects the original (still-running,

hidden) process is alive, logs second-instance: suppressing duplicate
argv, and hands off to it instead of starting fresh.

1. That handoff — which should just focus/restore the existing window —

instead triggers an unwanted full account/session refresh in the
existing process:

16:02:52  second-instance: suppressing duplicate argv
16:03:34  [growthbook] refreshing for account change
16:03:35  Loaded https://claude.ai (full reload)
16:03:36  ~50x blocked permission checks, all redirecting to
          claude.ai/login?...auth_kind=session_stale_relogin
16:03:38  [Auth] Using system browser for: /login/app-google-auth
16:03:54  second-instance: suppressing duplicate argv (again)

1. The live session is marked stale (session_stale_relogin) and I'm

bounced to Google re-authentication in the system browser, despite never
having actually logged out or the process ever quitting.

This exact sequence reproduced identically on two separate days in my logs,
each following the same close-window-then-reopen action.

Expected behavior

Closing the window shouldn't silently leave an invisible background process
running with no indication (no tray icon) that it's still alive. And if it
does stay alive, reopening via the launcher should just focus/restore that
existing window without refreshing account state or invalidating the
session.

Actual behavior

Reopening after a close forces a full Google re-login, every time, because
the "second instance hands off to existing process" path incorrectly
triggers an account/session refresh instead of a simple window focus.

Possibly related

#80494 (Linux Claude Desktop forcing relogin after reboot) — different
trigger (reboot vs. close/reopen) but same underlying symptom of the desktop
session not persisting on Linux.