Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I noticed that when I delete a local project I have worked on with Cursor, the chat history is also deleted. I assume this is Cursor’s default behavior once a project is deleted.
I understand the initial reasoning behind this. However, very often there are Git-related issues in a project, and the most pragmatic solution is simply to delete the entire folder and create a fresh Git clone. Of course, in an ideal architectural world, you would not delete it and would resolve everything properly through Git. But in practice, very often the fastest approach, instead of spending time dealing with various errors, is to quickly create a new clone and continue working.
The problem is that this causes the entire project chat history to disappear.
Because of that, I would like to suggest that this be handled differently. For example:
- the user could have an option to decide when to delete the history for individual projects, or
- by default, the history would not be deleted and would simply remain available.
I do understand the challenges here, especially the risk of corrupted or mismatched chats. For example, if we had a project called A, B, C, deleted it, and later created a new project with exactly the same name in the same location, the old chat history could appear for what is actually a different project. So I do understand the issue behind this.
That said, there must be some architectural way to think this through, whether through a unique identifier, giving the user the ability to control this via an option, or doing something with the threads.
In any case, if the entire history is gone, that is a bad outcome.
Steps to Reproduce
see desc
Operating System
Windows 10/11
Version Information
Version: 2.6.20 (user setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Early Access
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
Does this stop you from using Cursor
No - Cursor works, but with this issue