claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

[claude.ai] Conversation History Data Loss - Chats Randomly Disappear

Open sudoxreboot opened this issue 1 week ago • 5 comments

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

  1. Reliable persistence - Conversations should not disappear without user action
  2. Export functionality - Let users backup their conversation history
  3. Retention policy transparency - If there are limits, document them clearly
  4. Deletion warnings - Notify before any automated cleanup
  5. 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.

sudoxreboot avatar Dec 16 '25 21:12 sudoxreboot

I also experienced this issue.

MINSSERAPHIM avatar Dec 19 '25 17:12 MINSSERAPHIM

same

ssuawf avatar Dec 25 '25 11:12 ssuawf

Same, this is unacceptable, part of my code is rewritten but not finished and claude acts like it never happened

Rroobbbb avatar Dec 26 '25 01:12 Rroobbbb

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.

sudoxreboot avatar Dec 26 '25 01:12 sudoxreboot

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.

sudoxreboot avatar Dec 26 '25 01:12 sudoxreboot