[Bug] Deleted chats/agents reappear as BLANK in sidebar (v3.0.13 / Ultra)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am experiencing the “zombie chat” bug where deleted sessions reappear in my sidebar shortly after being removed. This is happening for both Today’s and Yesterday’s chats.

Steps & Symptoms:

I delete a chat/agent using the 3 dots > Delete menu (e.g., “Withdrawal verification for transactions”).

The chat is removed from the sidebar.

After a few minutes or an app restart, the chat reappears in the sidebar list.

Crucial Detail: When they reappear, they are completely blank. Before deletion, they had full histories, but the “resurrected” version is just an empty session occupying a sidebar slot.

System Information:

Plan: Ultra ($200/mo)

Model: GPT-5.2 (Agent Mode)

Machine ID: aa99c58b69381f04f47c7c449c549c5e079653bc8faaa4173c6162e1f9e3bb6a

Request ID: d93224bd-1e10-4e4e-b861-d12dea62daab

Version: 3.0.13 (user setup)

Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0

Date: 2026-04-07T03:05:17.114Z

OS: Windows_NT x64 10.0.26200

Steps to Reproduce

  1. Open the sidebar in Cursor IDE.
  2. Click the “three dots” (…) menu next to any chat session (Today’s or Yesterday’s).
  3. Select “Delete.”
  4. Restart Cursor or wait a few minutes while using the app.
  5. The deleted chat reappears in the sidebar but is now completely blank.

Expected Behavior

The chat should be permanently removed from the local sidebar and the server-side history. It should not reappear after being deleted.

Operating System

Windows 10/11

Version Information

Version: 3.0.13 (user setup)
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z

For AI issues: which model did you use?

GPT-5.2 (Agent Mode)

For AI issues: add Request ID with privacy disabled

d93224bd-1e10-4e4e-b861-d12dea62daab

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey @Janak_Vidyarthi! Thanks for the report. This a known bug and we landed two PRs last night to address it. Should be fixed soon!