Chat history lost for one project only; other projects unaffected

[superjinge (进哥 苏坡)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m reporting a data-loss issue with Cursor chat history.
What happened:
All chat/conversation history for one specific project/workspace is missing. When I open that project, previous chats no longer appear in the chat sidebar.

What still works:
Other projects/workspaces show their chat history as expected. The problem appears isolated to this one project.

Steps to Reproduce

Open the affected project.
Open the Chat/Composer sidebar.
Observe that all prior conversations are gone.

Expected Behavior

Chat history for this project should persist across sessions, like my other projects.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.5.38
VSCode Version: 1.105.1
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750
Date: 2026-05-26T21:32:06.537Z
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: Darwin arm64 24.6.0

Additional Information

after an update and restart

Does this stop you from using Cursor

No - Cursor works, but with this issue

[mohitjain (Mohit)]

After an update, the sidebar index that maps chats to their titles can get overwritten for a specific workspace, which is why you’re seeing “New Chat” entries instead of your actual titles. The good news is the underlying chat data is almost certainly still on disk.

To check, open a terminal and run:

ls ~/.cursor/projects/

Find the folder matching your affected project — inside it, check for an agent-transcripts/ directory with .jsonl files. If those files exist, your conversation data is preserved on disk even though the sidebar isn’t showing it.

A couple of things worth trying:

1. Reload the window - Cmd+Shift+P > Developer: Reload Window

2. Reopen the project using File > Open Folder with the exact same folder path you were using before the update

Our team is tracking this and working on a fix. Unfortunately there’s no manual reimport step available right now.

You may also find this related thread helpful - other users reported the same issue with additional recovery details.