fix: load /login instead of root so premature auth detection is prevented
Loading https://claude.ai as the start URL caused didFinish to fire on the landing page while stale/tracking cookies were already in WKWebsiteDataStore. The 'any claude.ai cookie' check then fired immediately, closing the login sheet before the user could sign in. Loading /login ensures the URL-guard catches the initial page load and only checks cookies after the real post-login redirect.
This commit is contained in:
+1
-2
@@ -3,7 +3,6 @@
|
||||
### Bug fixes
|
||||
- Fixed "Not signed in" showing incorrectly on launch when the session was already active
|
||||
- Sign-in state is now detected immediately from stored cookies on startup, before the first data refresh completes
|
||||
- Fixed Re-authenticate (and Sign In) not detecting an existing session — the login window now loads `claude.ai` directly so already-signed-in users are detected correctly and the window auto-dismisses
|
||||
- Fixed login window auto-closing before the user could sign in — the login window now correctly loads the `/login` page so it only detects auth after the actual sign-in redirect
|
||||
- Fixed "No API key configured" showing after signing out — now correctly shows "Not signed in" with a prompt to sign in
|
||||
- Added `/api/organizations` as a final fallback for org ID resolution when the bootstrap API response doesn't include it
|
||||
- Session cookie detection now checks both `sessionKey` and `__Secure-next-auth.session-token` cookie names
|
||||
|
||||
Reference in New Issue
Block a user