[Bug] Chat History Lost after Update

[ahchimlee]

Describe the Bug

After updating Cursor, I lost all my chat history.
I still have the backup of state.vscdb from the previous version (Last Updated Jan 5, 2026), but Cursor fails to migrate or recognize the old data.

My Analysis (Engineering Details)
I attempted a manual DB migration using sqlite3, but it seems the schema and internal dependencies have changed.

1. Old Data Location: My old chat history is stored in the key workbench.panel.aichat.view.aichat.chatdata.
2. Dependency Issue: It seems chatdata is tightly coupled with src.vs.platform.reactivestorage.browser.reactiveStorageServiceImpl.persistentStorage.workspaceUser (specifically tabId).
3. Migration Failure: Even after manually injecting the JSON data into the new state.vscdb, the UI does not show the past chats. It seems the tabId or workspaceId mismatch prevents loading the history.

Steps to Reproduce

1. Create some chat history with the AI in a specific project folder.
2. Update Cursor to the latest version. (The previous version was likely from before April 26, 2025)
3. Reconnect Cursor to the remote server.
4. Check the “Chat” pane.

Expected Behavior

Cursor should automatically detect the old state.vscdb or provide a way to import past chat history.

Please provide a migration tool or a fix for this backward compatibility issue.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.35 (user setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
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.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report.

Unfortunately, this is a known issue. Chat history doesn’t always migrate correctly between versions. The previous fix was for version 1.7+, but it looks like the problem is showing up again on 2.3.x.

I’ve passed this info to the team. Your technical analysis of the DB dependencies is helpful for debugging.