Why does Cursor keep asking me to sign in?
Common causes
Cursor keeps your account session for a while, and that session can expire or fail to save. Browser privacy tools, strict cookie settings, or a second browser profile can break the handoff between the browser login page and the editor. Corporate networks and VPNs sometimes block the callback step as well.
- Browser blocks third-party cookies or sign-in pop-ups
- Several accounts or browser profiles are open at once
- A VPN or firewall interrupts the login callback
- The editor is outdated and cannot read a newer session
Steps that usually help
Sign out from the Cursor menu, close the editor completely, and sign in again using the same browser where you normally work. If the browser asks to open the editor, allow it. Restarting your computer clears helper processes that can hold on to an old session.
When to dig deeper
If the loop continues, try disabling a VPN briefly or allowing the login domain through your firewall. Updating Cursor to the latest version also helps when the login flow has changed. If nothing works, the official support channel can check your account status.
Common mistakes
- Signing in with one Google account in the browser and a different one in the editor.
- Clicking sign-in again and again without closing the editor first.
- Blaming your password when the real problem is a blocked browser cookie.
