After upgrading Cursor from 1.7 to 2.0, all previous chat history disappeared (no chat content found in local DBs)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After upgrading Cursor from 1.7.54(or1.8.xx) to 2.0.14, the “Previous Chats” panel lists all past chat titles, but any selected chat stays on “Loading Chat” indefinitely and the body never loads. Re-opening the same thread from history reproduces the issue.

The titles remain, which suggests the index exists but the content cannot be fetched.

Environment: Cursor 2.0.14 (previously 1.7.54) on macOS darwin 24.6.0. Signed in: Yes. Multiple profiles exist under ~/Library/Application Support/Cursor/User/profiles/ (e.g., -419b7796, 2cc293f4).

What I tried: signing out/in and switching profiles did not resolve the issue; new chats can be created and viewed normally; local inspection of various storage (globalStorage state.vscdb and backups, Local/Session/WebStorage, .specstory/history) found UI-state keys but no stored body content.

Notes: Is there any change to chat storage or migration between 1.7 and 2.0? Since titles are visible, the index seems intact and only the body fetch fails. Please advise on the official storage location for chat bodies and any migration/resync procedures. I can provide a sanitized backup of the Cursor directory if needed. If there’s a recommended procedure to capture console/network logs via “Help → Toggle Developer Tools”, please let me know.

Steps to Reproduce

  1. Upgrade Cursor from version 1.7.54 to 2.0.14.
  2. In the AI panel, click any previous chat under “Previous Chats”.
  3. The chat title appears at the top but the body never loads and the center displays “Loading Chat” indefinitely.
  4. Re-open the same thread from the history list; the same issue occurs.

Expected Behavior

Existing chat content should load immediately and be viewable.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.14
VSCode Version: 1.99.3
Commit: b40d4b28058fede67ea231ab37a15cececd94b00
Date: 2025-10-26T19:20:51.222Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Previous Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue affecting chat history after recent version updates.

A few things that could help:

  1. Developer console logs: Open the chat panel, try loading a previous chat, then check Help → Toggle Developer Tools → Console for any errors. Please share a screenshot or copy the relevant error messages.

  2. Disk space check: Low disk space during an update can cause history loss. Was your disk nearly full during the upgrade?

  3. Backup check: Do you have Time Machine or another backup from before the upgrade? The chat database is located at ~/Library/Application Support/Cursor/User/workspaceStorage/

For now, new chats should work normally. Going forward, I recommend using Export Chat (right‑click a chat) to save important conversations as Markdown files before updates, or use the SpecStory extension.

Thank you for replying.

  1. When I check console log, → [composer] No composer data handle found [handleDeselectingComposer]
  2. could be this case, but there should have 10 - 15 gb spare storage space.
  3. Unfotunately, I haven’t do timemachine recently, so It’s gone.

Yes I have leant that I need to connect my timemachine storage for always…

1 Like