superdooper86
de71ec2794
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.
671 B
671 B
What's new in v1.2.1
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 login window auto-closing before the user could sign in — the login window now correctly loads the
/loginpage 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/organizationsas a final fallback for org ID resolution when the bootstrap API response doesn't include it