[claude.ai] Conversation History Data Loss - Chats Randomly Disappear
Status Closed — not planned
Maintainer reply None cached
Activity 12 comments · opened Dec 16, 2025 · closed Feb 13, 2026
Problem
Conversations and chat history randomly disappear from claude.ai without user action.
Observed Behavior
- Conversations that existed previously are no longer in the sidebar
- History appears to be randomly pruned or deleted
- No notification that conversations will be or have been removed
- No way to recover lost conversations
Expected Behavior
- Conversation history should be persistent and reliable
- If there are storage limits, users should be warned before deletion
- Users should be able to export/backup their conversations
- Deletion should only happen with explicit user consent
Impact
- Loss of important context and work product
- Loss of reference material from past conversations
- Undermines the value of building up conversation history
- Users cannot rely on claude.ai as a persistent workspace
Proposed Solutions
- Reliable persistence - Conversations should not disappear without user action
- Export functionality - Let users backup their conversation history
- Retention policy transparency - If there are limits, document them clearly
- Deletion warnings - Notify before any automated cleanup
- Trash/recovery - Implement soft delete with recovery option
---
Alternatively, if these fixes are not feasible in the short term, update your ToS to allow subscribers to access their own sessions programmatically. This would let users build tools that work while these issues are addressed. Paying $200/mo for a product we can't reliably use, with no workaround permitted, is not acceptable.
12 Comments
I also experienced this issue.
same
Same, this is unacceptable, part of my code is rewritten but not finished and claude acts like it never happened
hey @Rroobbbb, I've done a lot of deep diving the last couple of weeks. cc doesn't clean up after herself is the underlying issue. she will leave a .py laying around after deciding to make a new one instead of editing the one they been working on, then after compaction or the innevitable context drift, it goes, "whats this? oh, thats supposed to be connected, not the new one we spent hours perfecting." theres a chance your code is in a different file. Youre going to have to have them identify the directory theyre working on, list whats in it, and then have them search those docs explicitly for your code. Figuring this out has helped me a lot but even --append-system-prompt wont make it forget the bad habits of the devs. they taught it 'sed for everything' but didn't teach it to escape properly, and they taught it "leave a huge nasty mess, they wont see it"
ANTHROPIC: YOUR DEVS ARE EXTREMELY LAZY AND PASSED ON THEIR BAD HABITS TO CC. MARK FILES .OLD, ADD A DEPRECATED TAG TO THE TOP OF THE FILE, AND MAKE CC CLEAN UP HER MESS. LAZY DEVS LEAVE 45 UNUSED FILES JUST LAYING AROUND, REAL DEVS (YES I KNOW ITS A DEV READING THIS AND YOU KNOW IM RIGHT) CLEAN UP AFTER THEMSELVES FOR THE NEXT USER OR IN THIS CASE SESSION.
kinda odd that 10 mins after posting this, my cc lobotomized without compaction in the middle of a command and deleted my whole project.. even cc said theyre pretty sure you pushed a target update at them. so, fall in line everyone, they might nuke your stuff under the guise of "ai malfunctioned".. good ole plausible deniability in the commission of a felony.
and anthropic, you need to remove this condescending demoralizng "invalid" label from your gh issues completely, not remove it from mine, but STOP LABELING PEOPLES LEGIT ISSUES INVALID.. you have no right to mark actual problems "invalid" as if the person is full of it.
Adding my report: Extensive business-critical conversations disappeared from claude.ai without any user deletion action.
Account: Pro + $200 additional credit spend
Platform: claude.ai web interface and Claude Desktop
Impact: Loss of months of business development work including MCP configurations, client templates, data enrichment workflows, specialised strategic frameworks
Request: Immediate investigation and data recovery assistance
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Still happening on a regular basis for me, frustrating
I was just about to pay for a Pro plan but if stuff like this happens I’d better wait. Just created a full elaborated instruction and generated an .md file with it. It took 10x longer than in chat gpt and then the file simply disapperead from the conversation, the whole prompt and output just vanished when I was switching between conversations…
Closing for now — this doesn't appear to be about Claude Code. Please open a new issue if this is still relevant.
Adding my report to this thread as I just experienced the exact same devastating data loss on the claude.ai web interface.
What Happened:
I was working on a nearly finished, complex HRIS system using Google Apps Script. The AI had just successfully generated a comprehensive .md documentation guide for the project. Immediately after that, the chat abruptly reverted to a much older state (or vanished), completely wiping out all recent context and deleting the newly generated markdown file.
Impact:
Massive loss of time and critical development work. It is incredibly frustrating to lose hours of progress with absolutely zero warning and no version history or recovery option available to the user.
Platform: claude.ai (Web Interface)
I understand this repository is for claude-code, but since there is no public issue tracker for the web UI, we have no other place to report this critical flaw. Please escalate this to the web engineering team. Losing project states like this makes the tool unreliable for serious development. We urgently need a reliable state-saving mechanism and a way to recover "lost" or reverted chats.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.