Claude Code Conversations Disappear Without a Trace
Claude Code users are expressing their frustration as the application has been discreetly erasing conversation records. If you haven’t modified your default configurations, your discussions may already be lost. The discontent is evident on Claude Code’s GitHub page, where numerous issues have emerged in recent months, all highlighting the unexplained vanishing of conversation records.
The Enigmatic CleanupPeriodDays Setting
At the center of this uproar is the cleanupPeriodDays setting. By default, it is configured for 30 days, and every time Claude Code is launched, it performs a cleanup. Any .jsonl files older than 30 days are deleted. Anthropic, the organization behind Claude, asserts it’s the users’ fault for not reviewing the documentation, emphasizing that the 30-day deletion is a security protocol established since Claude’s launch.
Security vs. Usability
Anthropic articulated, “Retaining plain text transcripts indefinitely poses a risk, as they may contain sensitive information such as source code and credentials. The 30-day default strikes a balance between resuming work and limiting data retention.” Reasonable enough, but the issue lies in users not being informed about this impending deletion. No notifications, no warnings, nothing. Just a quiet removal every time the app is started.
GitHub Users Contribute Their Thoughts
GitHub user FTSBrand expressed disappointment, “Cleanup occurs automatically without any disclosure at installation or during the first run.” Users, viewing their chat history as reliable information, are unwittingly setting themselves up for distress when their valuable notes disappear without notice.
Recovery? Not Likely
This enigmatic cleanup is harsh, with no way to recover lost data, no grace period, and not even a record of what has been erased. Even efforts to extend the retention period are currently nonfunctional, as reported by frustrated users like ojura. The core issue is that deletion is linked to the modification timestamp of the transcript, not the actual last activity date.
Backup Solutions
Some resourceful users have proposed saving transcripts to evade this digital execution, but that serves as a workaround, not a solution. As GitHub user caioribeiroclw-pixel highlights, “Backups are beneficial, but they cannot substitute for essential product-level transparency regarding a destructive retention process.”
Conclusion
Who Needs a Detective When You’ve Got Claude?
Thus, there you have it – a digital enigma fit for Sherlock, brought to you by Claude Code. Until this is resolved, tech aficionados should prioritize secure backups and maybe get a magnifying glass to sift through those elusive documentation details. Here’s to contemporary coding journeys!
