Cursor IDE Keeps logging out

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since the last few updates, I am constantly getting logged out of the IDE. I don’t know what’s going on it’s like the session is set to 30 min or something, and opening new editors, means I have to then log in again. Worse yet there isn’t even a clear indicator that you are NOT logged in, the chat just sits there until you reopen the editor and try to chat again, and then it will finally prompt you to log back in.

Steps to Reproduce

Nothing special just use the editor. It’s some kind of regression with the last updates.

Expected Behavior

I should not have to log in more than once in a month or whatever it was before.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.39
VSCode Version: 1.99.3
Commit: a9c77ceae65b77ff772d6adfe05f24d8ebcb2790
Date: 2025-10-08T00:33:20.352Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.14.0-33-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

6 Likes

Yeah I am encountering this issue as well and for some reason this is actually due to the last few updates - for reference I am on linux and using appimage

2 Likes

same issue

1 Like

same

1 Like

Hey, thanks for the report. We’ll check this.

5 Likes

Same issue on Ubuntu 24.04 using appimage

1 Like

Has there been any progress on this? What I’ve noticed that it won’t allow me to be logged in, in more than one instance at once. I have two editors open, and it will log into one, and log out of the other.

FWIW, I do not have this issue. I’ve been asked to log occasionally…maybe after an update or crash?… but I run two windows and have no issue. Are you opening a new window from inside cursor (what I do) or launching two from outside?

It seems a linux issue maybe? It happens if I open the window via OPEN RECENT, or if I do Open With Cursor (Right Click In Folder).
But like I said this is something recent that started happening. Maybe about 2 weeks ago? it seems like there was a new version being released every day, there was a lot of updates and installs, and since then this bug has been showing up.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.