Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Guys, FFS… I am having to revert back to 1.7 for the SECOND TIME after downloading 2.0 when it came out, saying oh hell naw, then going back to 1.7… waiting a while, and now downloading 2.1 only to be going back to 1.7 again. My last post got zero feedback from admins. Lost chats, chats retitling themselves, files closing, changes reverting (Reinstalling 1.7)
I repeat, I can’t see any of my prior chats dude. Whenever I download anything past 1.7 all my prior chats are wiped. THIS time around, it won’t even let me see a chat that I just created after I click off of it for the first time. I’m not posting a picture because there’s nothing to see. It’s the chat view with “Loading Chat” pulsing in the middle, and the chat selected that I just created. This is what was happening to any OLD chat I would click on prior to updating this time, but now ANY chat, old and new, are all biffed. I’m a paying user who would really love to be able to use the newer software and take advantage of the new stuff—but I can’t. So for that reason I’m going to say YES this keeps me from using Cursor, while I patiently wait for 2.x to deliver.
UPDATE: Now the same issue was happening last time that caused me to drop 2.0 completely, but now in 1.7. When I click on a chat, it just disappears that chat completely. Doesn’t archive it—it just goes away. Meaning, the app is unusable. Chats cannot be clicked because they disappear when clicked. I am going to uninstall and reinstall and see if that fixes it.
Steps to Reproduce
Uh, make a chat. Click off of it to another chat that DOESN’T load. Go back to chat you just made. Stare at “Loading Chat” for infinite amount of time.
Update: Select any chat—that chat disappears.
Expected Behavior
To be able to see the chat and use it.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.25 (user setup)
VSCode Version: 1.105.1
Commit: 7584ea888f7eb7bf76c9873a8f71b28f034a9820
Date: 2025-11-23T04:45:23.529Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Yes - Cursor is unusable