MASS FAILURE: Conversation data missing / missing blobs on ALL chats

Support Bug Reports
1

Hi Cursor Support,

I’m reporting a mass failure of Agent/Chat conversations on my account.

Summary

Almost every existing chat shows:
“Conversation data missing — This conversation’s data is missing and can’t be restored. Start a new chat to continue. (N missing blobs: …)”

This is not a single broken conversation. It currently affects essentially ALL of my past chats, which blocks continuing ongoing project work.

Request ID

26093860-160d-4a23-9550-e0732d0065ff

(from the error banner; Copy ID was available)

Environment

  • Cursor IDE Version: 3.13.25 (stable)
  • Commit: 31e8d61c448c7472e371505838a0fe34083dad50
  • OS: macOS 26.4.1 (darwin 25.4.0, Build 25E253)
  • Model in use when seen: Cursor Grok 4.5 High Fast (also seen across other chats)

Actual behavior

Opening existing Agent chats shows the non-retriable “Conversation data missing / N missing blobs” banner. Continuing those conversations is impossible.

Expected behavior

Existing conversations should load and continue normally; blob storage for conversation state should remain available.

Notes

  • Fresh/new chats still work.
  • This matches the known server-side “missing blobs / Blob not found” issue discussed on the forum, but severity here is account-wide (all chats), not one-off.
  • Using @Past Chats against a broken conversation also breaks the new chat (known cascade).
  • Local agent transcripts under ~/.cursor/projects/*/agent-transcripts still exist, but the UI/server conversation state cannot be restored.
  • Clearing local cache / reinstall is not a valid workaround per your prior forum guidance.

Please investigate the Request ID and the blob-store state for my account. Happy to enable Share Data temporarily if needed for deeper debugging.

Thanks,
Stefan Foelser
Ground UP GmbH

6

Hey Stefan,

This banner often shows even when the data is still on your disk and just couldn’t be read in that moment, so it’s worth trying to bring them back before assuming they’re gone:

  1. Fully quit with Cmd+Q (not a reload), reopen, and try the affected chats again.
  2. Update to the latest version (Command Palette → Attempt Update).

Please don’t clear Cursor’s data, delete state.vscdb, or reinstall - that would wipe conversation data that may still be recoverable (you already flagged this, and you’re right).

For any that still fail after a full restart, that data is genuinely gone and can’t be restored - this history lives on your machine, not our servers. You can copy context from the transcripts in ~/.cursor/projects/*/agent-transcripts into a new chat, but they won’t revive the old session. One thing to avoid: pointing @Past Chats at a broken chat, since it can carry the problem over.

This isn’t anything you misconfigured - it’s on our side and we’re tracking it. Does a full restart bring any chats back? That tells me how many are recoverable vs. gone.