Chat history wiped out and empty markdown export after clicking "try again" during a "reconnecting" error

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During a chat session, specifically when submitting my second prompt, the UI suddenly displayed a “reconnecting” status. Shortly after, a prompt appeared asking me to “try again”. After clicking “try again”, the entire conversation history was completely cleared from the UI.

Furthermore, when I attempted to export this broken conversation to a Markdown file, the resulting document was empty, containing only the chat title and timestamp, with no actual conversation content.

It’s not just in this version; I’ve encountered this issue once or twice before as well.

Steps to Reproduce

  1. Start a chat and submit a first prompt.

  2. Submit a second prompt in the same chat.

  3. The IDE encounters a connection issue and displays “reconnecting”.

  4. A prompt to “try again” appears. Click the “try again” option.

  5. Observe that the entire chat history disappears.

  6. Attempt to export the current chat to a Markdown file.

  7. Open the exported file and observe it only contains the title and timestamp.

Expected Behavior

Clicking “try again” after a connection issue should either retry generating the response or restore the connection without deleting the existing chat history. The previous conversation should remain intact. Additionally, exporting the chat to Markdown should output the full conversation history up to the point of the error, rather than an empty file.

Screenshots / Screen Recordings

2026-04-17_155625111.png
2026-04-17_155625111.png1912×979 29.2 KB

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (user setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Early Access
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Composer 2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report.

This is a known issue. If you click Try again after a reconnecting error, a race condition can happen and wipe your chat history. The empty Markdown export is a direct result of the same bug. The data is already gone from memory, so there’s nothing to export.

The team is aware of this. There’s no timeline yet, but your report helps us prioritize it.

As a temporary workaround, if you see reconnecting, it’s better to wait for the connection to come back instead of clicking Try again. This makes it much less likely you’ll lose the history.