Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Is anyone else experiencing login issues with Cursor today?
My Cursor Desktop app was suddenly logged out. When I click to log in, it opens the browser and I can successfully log in on the web page. However, the login status never syncs back to the desktop app.
I just tried it again and the issue still persists. It seems like the login callback from the browser is failing to reach the Cursor Desktop application.
Has anyone encountered this or found a workaround? Any help would be greatly appreciated!
Steps to Reproduce
Steps to Reproduce:
Open the Cursor Desktop application (which is currently logged out).
Click the “Log In” button within the desktop app.
The default web browser opens. Successfully log in to the Cursor account on the web page.
The web page attempts to redirect/callback to the desktop app.
Return to the Cursor Desktop app and observe the login status.
Expected Behavior:
The desktop application should recognize the successful web login, sync the status, and log me into the app.
Actual Behavior:
The desktop application remains completely logged out. The login callback from the browser to the desktop client appears to fail silently, making it impossible to use the app with my account.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Version: 3.1.17 (user setup)
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200
For AI issues: add Request ID with privacy disabled
Request ID: ef079c40-0646-4359-9c37-769708f025a2
Authentication error If you are logged in, try logging out and back in.
YXe: Authentication error If you are logged in, try logging out and back in.
at jpA (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32115:44580)
at WpA (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32115:43786)
at ZpA (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32116:5088)
at Ool.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32116:9098)
at async s$o.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44360:8423)
at async zOl.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44408:8884)
at async zOl.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44408:9837)
at async yLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32182:15752)
at async Object.Gs [as onSubmit] (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43415:4781)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43389:57281
Does this stop you from using Cursor
Yes - Cursor is unusable