I lost thirty days of Claude Code sessions last week. Just gone. No warning email, no “your files are about to disappear” notification, nothing. I was sitting there looking for a conversation I’d been having with the AI about restructuring my side project’s architecture, and it vanished like it never existed. That’s when I realized what was happening-and honestly, I’m still annoyed about it.

Why This Keeps Coming Up

Most of us GenXers learned to build things by saving obsessively. Floppy disk. External hard drive. Cloud backup. We know the world doesn’t preserve your work unless you force it to. But somewhere along the way, we started trusting that digital platforms would just keep our stuff, and Claude Code let us believe that without any real warning.

The thing is, it’s not malicious. Claude Code has a built-in cleanup timer that automatically deletes inactive sessions after thirty days. That’s the actual policy, sitting there in the settings nobody reads. I’m guessing Anthropic did this for server management and cost reasons, which is fine, but they buried the detail in a way that caught a lot of people off guard. Including me.

And here’s the kicker-when I started asking around in the AI builder communities, I found out I wasn’t alone. This was happening to people constantly, and most of them had no idea why their sessions were disappearing.

What I Actually Found Out

Once I got over being annoyed, I actually dug into the Claude Code settings and found the culprit: a value called `cleanupPeriodDays` that’s set to 30 by default. That’s it. That’s the timer. Your sessions are on borrowed time unless you change it.

The fix took me about two minutes. I went into the settings, located that variable, and bumped it up to 365. You could go higher if you wanted-I’ve seen people set it to 730 for two years or just make it something ridiculous. The point is, you have control over this, but you have to actually do it. It doesn’t happen automatically.

Once I fixed that, I realized I still needed a better system. Thirty days of recovered sessions is one thing, but if I’m going to keep doing AI-assisted work, I need my thinking documented somewhere it actually sticks around. So I started using Claude to auto-summarize the important conversations and push them into a GitHub repo. Now my project thinking lives somewhere permanent-somewhere I can actually find it later when I need to remember why I made a decision.

What You Can Do With This Today

First, go into your Claude Code settings right now and change that `cleanupPeriodDays` value. Set it to something reasonable-at least 365 if you’re doing actual work. This buys you time and gives you breathing room while you figure out a better long-term system.

Second, if you’ve got sessions you care about, grab them before they disappear. Don’t assume they’ll still be there in three weeks. Download them, screenshot them, copy the text-whatever makes sense for your workflow.

Third, and this is the smarter play, start thinking about where your AI-assisted work is actually supposed to live. For me, it’s a combination of GitHub repos and Notion. For you, it might be different. But the key insight is that you can’t rely on Claude Code’s session history as your permanent archive. It was never designed to be that.

This is the kind of thing that feels obvious once someone tells you, but nobody puts it in the welcome email. We’re still figuring out how to live with AI as a professional tool, and that means figuring out stuff like data retention on our own.

Take the two minutes. Change that setting. Your future self-the one who actually needs to remember that conversation-will thank you.

Watch the Full Video

I covered all of this in a short video too – sometimes it’s easier to watch than read.

Watch on TikTok →