Hi, I’d like to add a more precise description of the issue, as I’ve narrowed down the behavior further.
What actually happens:
When I trigger the login flow from the Cursor desktop client, the in-app Browser Tab opens and shows a “Sign in to Cursor” dialog with a “Continue to sign in” button (see attached screenshot). When I click that button, one of two things happens:
A loading spinner appears briefly, then the page immediately redirects back to the same “Sign in to Cursor” dialog without ever showing the username/password input screen.
Occasionally, it does proceed to the username/password page — but after I enter my credentials and submit, it redirects back to the same “Sign in to Cursor” dialog again, rather than completing the login.
In other words: I can never reach the https://cursor.com/agents page at all. The flow keeps resetting to this initial “Continue to sign in” screen, forming an infinite loop that never successfully authenticates.
What I’ve tried:
Clicking “Continue to sign in” repeatedly — always loops back.
Completing credentials when the password page does appear — still loops back to the same dialog.
Using an external browser (Chrome) — this works fine and completes login successfully, so the credentials are valid and the account is active.
Screenshot attached:
The dialog I keep getting returned to is shown in the attached image: a Cursor-branded sign-in popup with “Sign in to Cursor” heading, a cancel button, and a blue “Continue to sign in” button.
This seems like the in-app Browser Tab is failing to handle the OAuth redirect correctly, possibly due to the window-scoped tab ownership issue mentioned in previous reports. The tab appears to be stuck with a stale session or context that prevents the OAuth flow from progressing past the initial consent screen.
Any insight or fix would be appreciated — for now, I’m using an external browser as a workaround, but the in-app experience is clearly broken.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
I’m experiencing a login loop issue specifically within the in-app Browser Tab, and I’d like to report it.
Bug Report Template
Where does the bug appear (feature/product)?
Account, billing & login
Describe the Bug
When attempting to sign in to Cursor from the desktop client, the in-app Browser Tab opens and shows a “Sign in to Cursor” dialog with a “Continue to sign in” button. Clicking this button causes the OAuth flow to loop indefinitely — the page either reloads back to the same “Continue to sign in” screen without ever showing the credential entry page, or occasionally shows the username/password page but then redirects back to the same “Continue to sign in” screen after submission. I never reach cursor.com/agents or any post-login dashboard. Using an external browser (Chrome) works perfectly, so this issue is specific to the in-app Browser Tab.
Steps to Reproduce
Open Cursor desktop client and navigate to Settings → Sign In.
The in-app Browser Tab opens with a “Sign in to Cursor” dialog containing a “Continue to sign in” button.
Click the “Continue to sign in” button.
Observe that the page shows a loading spinner briefly, then reloads back to the same “Sign in to Cursor” dialog.
(Occasionally) If the credential page does appear, enter valid username/password and submit — the page then redirects back to the same “Continue to sign in” dialog again instead of completing the login.
Expected Behavior
Clicking “Continue to sign in” should proceed to the credential entry page (if not already authenticated via browser session), and after submitting valid credentials, should complete the OAuth flow and return the desktop client to a logged-in state, ideally redirecting to a stable dashboard (e.g., cursor.com/agents) or closing the browser tab.
— shows the “Sign in to Cursor” dialog with “Continue to sign in” button that I keep getting returned to.
(Please attach your image file here)
Operating System
Windows
Additional Information
Context that may be relevant:
This issue only occurs in the in-app Browser Tab. Using an external browser (Chrome) for the same login flow completes successfully, confirming that credentials and account are valid.
I suspect this may be related to the window-scoped browser tab store behavior previously reported by other users. Specifically, multiple agent chats within the same Cursor window share a single browser tab, and the tab’s ownership is re-stamped to whichever agent is currently active. In my case, the shared tab may be carrying a stale session/context from a previous agent (e.g., “Home” or another project), which interferes with the OAuth redirect handling and causes the loop.
I’ve seen a stable-browser-session/<hex> ID tied to the original root workspace, confirming that the tab is not being properly isolated per workspace.
Workarounds I’ve tried:
Hard refresh (Cmd+Shift+R / Ctrl+Shift+R) — no improvement.
Clearing browser cache/cookies within the in-app tab — no improvement.
Using an external browser — works reliably.
Closing all other chats/projects in the same window and retrying — sometimes helps but not consistently.
Does this stop you from using Cursor?
Sometimes - I can use an external browser to log in, so Cursor itself works after authentication, but the in-app login experience is broken and forces me to work around it.
Thanks for looking into this — happy to provide any additional logs or details if needed!
Hey, thanks for the detailed write-up. A couple key points that help clarify what’s going on:
Cursor sign-in always opens in your system default browser. There’s no built-in login tab inside the app. What you’re seeing in the screenshot is the normal browser sign-in page, not an in-app tab. So the window-scoped tab idea doesn’t apply here.
Since sign-in works fine in Chrome, the simplest path is:
Set Chrome as your system default browser, then click Sign In in Cursor again. The flow should open in Chrome and complete correctly.
Try to finish signing in within a couple minutes after clicking Log In so the app can pick up the session.
Check your email, including spam. If you get a verification code during sign-in, you need to complete that step or the session won’t be created and you’ll get sent back to Continue to sign in.
If it still loops after that, it’s likely an account-level check and a different team handles it. Email [email protected] so they can look at your account and unblock sign-in. Let me know if the Chrome workaround helped.
I followed your suggestion and set Chrome as my system default browser. However, the issue still persists — and I’ve recorded a video to show exactly what happens:
I click Log In in Cursor.
Chrome opens automatically with the Cursor sign-in page.
I enter my credentials and complete the verification.
After that, I’m redirected back to the Cursor app, but it shows the “Sign in to Cursor” page again.
When I click “Continue to sign in”, it just loops back to the same page — no success.
So even with Chrome as the default browser and completing the login within a short time, I’m stuck in this loop.
Could you please take a look at the video I’ve attached? It clearly shows the entire flow. At this point, I suspect it might be something account-related, as you mentioned earlier.
Would you be able to escalate this or check on your side? If needed, I can also reach out to [email protected] directly — but I wanted to follow up with you first since you were already helping me debug this.
Happy to provide any additional logs or details if that helps.
Thanks for the video and for trying the Chrome setup. That confirms what we suspected: your credentials are valid and sign-in works, but the session isn’t being created after the login step. That’s why you keep getting sent back to Continue to sign in. This is an account-level check, not a client issue, so I can’t unblock it from here.
Next step is to email [email protected]. They can review your account and clear the block so sign-in completes. Feel free to link this thread and mention you already tried the Chrome default browser workaround so they have the context.
Me too, encountered the same problem. It’s because I updated the version. Not sure if it’s due to a serious bug in the latest version, currently unable to log in.
I’m experiencing the exact same issue here.
I am on the Ultra subscription and have been completely blocked from working for over 3 hours now.
In the Cursor app, when I try to run a prompt, I get this error:
“Unauthorized request. User is unauthorized” (Copy Request: 26171d81-3968-46ac-9136-588f588fec99).
I went to the website and successfully logged in using my email and password, but now the https://cursor.com/agents page is stuck in an infinite reload loop.
Checking the browser’s network tab, I can see that requests to endpoints like https://cursor.com/api/dashboard/get-me and https://cursor.com/api/auth/me are all failing with a 401 Unauthorized status.
Looks like a global issue with session validation.
I’m experiencing the exact same issue described by Eric above — this seems to be a widespread bug, not an isolated case.
My experience matches point by point:
Login flow opens the “Sign in to Cursor” dialog
Clicking “Continue to sign in” either loops back immediately, or lets me enter my credentials and then loops back to the same dialog anyway
I can never complete authentication and reach my account
This happens both in the desktop app and on cursor.com directly in a regular browser
Additional detail that might help debugging: I can log in normally to a different Cursor account that has no subscription. The issue only occurs with my account that has an active Pro+ subscription. This might suggest the bug is related to how the OAuth flow handles accounts with active paid subscriptions specifically.
Referring to the author’s opinion mentioned earlier, after I switched from Edge to Chrome, I was able to log in; if there are other folks who can log in successfully on the Edge browser but can’t get into the Cursor client, you can give this a try.
For Eric, the login gets stuck on the account verification step. For you, it’s a 401 on cursor.com/agents (get-me and auth/me) plus Unauthorized request. User is unauthorized even though you have an active paid subscription. This is an issue we’re tracking and it affects some paid accounts. I can’t share an ETA yet.
To get your specific accounts unblocked so login works again, email [email protected] from the email on your account and include the Request ID if you have one. @amy_hun, you already have it: 26171d81-3968-46ac-9136-588f588fec99. The unblock is done at the account level, and I can’t do it from this thread.
To avoid mixing two different cases in one thread, please start a separate thread for the 401 loop on a paid subscription. That makes it easier to track your issue.
@kaihong_public1, thanks for coming back with results. Switching the default browser from Edge to Chrome does help some users with this loop, which is useful for others to know.
