How are you backing up your AI workspace?

I spent this week hardening my workspace setup and fell down the backup rabbit hole. Sharing the thought process because I want to know what everyone else is doing.

My whole workspace lives under local git. I don't keep it there for code reasons. The win is auditing: every change is signed, human or agent, and I can see exactly what the AI did each session and roll any of it back. Once you let agents write into your folders, that flight recorder stops feeling optional.

But git pulls a thread. A live repo can't sit inside OneDrive or iCloud. Sync engines fight the history layer: conflicted copies, placeholder files the agent can't actually read, endless re-upload of thousands of tiny .git objects. So the workspace has to move OUTSIDE the one backup most people already have. Which means backup now needs its own answer.

The thing that clicked for me: a backup has to answer two different questions. "Give me my files back" and "give me my history back." Most setups only answer the first. OneDrive only answers the first.

My own answer is three layers (external drive snapshot, remotes for the code, encrypted offsite for history) but I'm the nerd who enjoys that. The version I keep kicking around for everyone else: the agent zips the whole workspace, history included, and drops a dated zip into the OneDrive folder you already pay for. Keep the newest two, delete older. Sync can't host a live repo, but it carries a dead zip just fine.

So what are you actually doing?

Do you run git over a non-code workspace, and was the auditing worth the extra layers?

What is your backup story for the folders your agents work in?

Has OneDrive or iCloud alone ever actually saved you, or does it just feel safe?

1 comment

How are you backing up your AI workspace?