Cursor does not let the user use google SSO to log in to an app. No matter how you do it, it will not work. This bug has existed since the release of the browser feature.
Hey, thanks for the report. This is a known limitation of Cursor’s built-in browser. It runs as a sandboxed Electron webview, which blocks window.open(). Google OAuth uses a popup-based flow, so after the consent screen nothing happens.
For now, the workaround is to open the localhost URL in a regular browser like Chrome, Safari, or Firefox. Google Sign-In should work right away.
I’ve passed this on to the team. There’s no ETA yet, but your report helps with prioritization.
Unfortunately, there aren’t any other options inside the built-in browser right now. The issue is that Google OAuth uses a popup window.open(), and the sandboxed Electron webview blocks it. This isn’t something you can fix with a setting, it needs changes to the browser tool itself.
It’s crazy that this is still not solved. Most of the B2B companies out there rely on Google login, and a large part of them as the primary login option. Right now I can’t even use cursor browser and its Design mode, due to this limitation. Such a shame
Hey @yjallouli, this is a known bug, and we already have an issue open for it (see above in the thread). I can’t share a fix timeline yet since the ticket is in the backlog with low priority, and follow-up reports like yours really help us reconsider that, especially given the B2B case with Google login + Design mode.
For now, the only workaround is to open localhost in a regular browser like Chrome, Safari, or Firefox. The OAuth flow works fine there. I know that’s not a real option for Design mode. If there’s any update on a fix, I’ll post it here.
I want to add that this is also a problem for MSAL with Azure. This issue isn’t limited to Google SSO and is likely impacting a huge portion of users who use any kind of enterprise sign in solution.
@zackttaylor, good catch. The root cause isn’t specific to Google. The built-in browser blocks window.open() popups in a sandboxed Electron webview, so any popup-based OAuth flow breaks the same way, including Google, Microsoft MSAL, and many enterprise IdPs. I’ll expand the ticket scope internally so this is clearly captured. Thanks for the datapoint, the B2B impact really helps with prioritization.
No ETA for a fix yet. The workaround is the same, open the localhost URL in a system browser like Chrome, Safari, or Firefox. For MSAL specifically, if you control the app registration, you can temporarily switch from the popup flow to the redirect flow, use loginRedirect instead of loginPopup. That will work in the built-in browser until the fix lands.