Unable to restore chats when resetting settings due to Cursor crash

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I encountered a reset of settings and chats on my current Nightly Cursor, and the Doctor in my CursorMover said everything was fine.

Version: 2.4.0-pre.41.patch.0 (system setup)
VSCode Version: 1.105.1
Commit: e62153373d5f281ae01af6e3d66e0bcef1e5e830
Date: 2026-01-16T08:27:33.020Z
Build Type: Stable
Release Track: Nightly
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.22631

I tried to modify CursorMover and, with GPT-5.2 and Opus, we eventually came to the conclusion that when resetting the settings, the session is reset → the IDE requires authorization → a new access key for chats is generated → old chats cannot be opened, because the new access key does not work for them.

I also tried to embed a chat in the Cursor DB to simulate restoring chats from a third-party autobackup, but it didn’t work - so I can’t create an autobackup.

CHAT_RECOVERY_REPORT.zip (4.0 KB)

I’ve left the code for this CursorMover update attempt in the CursorMover repository, along with a document from the Agent describing what was tried. @deanrie, I would be grateful if you could pass on detailed information to the team.

Steps to Reproduce

  1. The Cursor agent can’t launch a Legacy Terminal.
  2. It has to launch New ■■■■■■ Terminal.
  3. The terminal left a zombie process after stopping the request and even after closing the terminal.
  4. You closed the process manually, but before that, you also closed the terminal.
  5. Cursor can’t open New ■■■■■■ Terminal for the same agent twice in a session, so you restart Cursor.
  6. After restarting, Cursor resets your data and asks you to log in.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.4.0-pre.41.patch.0 (system setup)
VSCode Version: 1.105.1
Commit: e62153373d5f281ae01af6e3d66e0bcef1e5e830
Date: 2026-01-16T08:27:33.020Z
Build Type: Stable
Release Track: Nightly
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.22631

Additional Information

It’s possible the bug occurs when attempting to open the IDE too quickly after closing it. I recommend the developers add some kind of blocker for this action - perhaps this bug will become even less common.

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
Cursor Mover: Copy the workspace without losing the chats
3

Thanks for the detailed report and investigation - I’ve flagged this for the team to review.

1 Like