This chat was created in an older version of Cursor and is no longer supported. Please start a new chat

Support Help
1

Request ID: d98363fa-8c99-4058-a4a8-e9de2ab9a718

{“error”:“ERROR_CUSTOM”,“details”:{“title”:“Chat Too Old”,“detail”:“This chat was created in an older version of Cursor and is no longer supported. Please start a new chat.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:[],“planChoices”:[]}}

This chat was created in an older version of Cursor and is no longer supported. Please start a new chat.

1 Like
4

I need help with cursor chat history.

6

Hi @Prajwal_Raj ,

This is a known compatibility issue that occurs when chats created in an older version of Cursor (≤2.3) are opened after an update across major versions. The chat data is still stored locally, but a server-side session token needed to continue the conversation gets lost during the update because the migration doesn’t run automatically.

Potential workaround: Try downloading Cursor v2.4 from cursor.com/downloads, open and interact with the old chats you care about at least once in that version, then upgrade back to the latest version. This can trigger the migration that preserves those chats going forward.

If that doesn’t work (the session token may already be unrecoverable depending on how old the chats are), you can still view and export your old chat content – you just won’t be able to send new messages in those conversations. Starting a new chat will work normally.

A community member posted a detailed technical analysis of this issue, and the team is aware of and tracking it.

7

This seems like kind of a silly issue. How can a chat be incompatible? It’s just a bunch of text. Why can’t it just copy and paste the text into the current chat engine? I don’t see how this is any different than summarizing the chat which it does regularly