Cursor not useable

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Chat history continually wiped from updates. Almost every update I have applied wipes my entire chat history. This is a problem because we PAY FOR THOSE TOKENS. This is a kin to buying a candy bar and having the doorman take it out of your hand as you leave.

Our chat histories are not some luxury. They are integral to the process. This is a simple issue. If you need an engineer to solve it I will do so.

Specstory is not the solution. (love the extension) NOT THE SOLUTION

Simplest approach, allow us to setup our own managed database built into cursor chat function.

Unequivocally Unacceptable.

Steps to Reproduce

Update the Application

Expected Behavior

Keep what you PAID for.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.1 (user setup)
VSCode Version: 1.99.3
Commit: 99e3b1b4d8796e167e72823eadc66ac2d51fd400
Date: 2025-08-21T00:21:08.834Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

At NO time should a datafile be wiped or inaccessible from an update.

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

I say this out of love and respect to the cursor team!

This is frustrating because of the complexities of my workflow.

Chat history use is critical to working through large complex codebases.

Building context for each aspect of a project in the proper way. Losing this data to the void is a waste of both of our resources. Efficient token use benefits both parties. This “BUG” adds extra pressure to the system and wastes tokens for such a simple issue.

If the team does not have the time or resources to address this, please allow me to fix it.

@condor

hi @Daniel-PHC thank you for the bug report. I will forward it to our team.

I agree that the chat history should not be wiped, but that may be an issue for which we need more info on cause as this is not an intended case.

@condor Thank you for the attention to this matter. Happy to help let me know what you need. I’ve been reporting this for 8 months. Now that I’m working on these types codebases in production this has become a big issue.

Happens during the login process as well. Random logout in the middle of work. please sign in button pops up and IF i sign in via prompt chat history wiped. If i close the application and restart I stay logged in and so does my history.

I assume this is happening during update as well. Have them look into the login process and connection back to the datafile.

Let me know what information you need to get this solved please.

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