How to protect a folder before letting ChatGPT or another AI edit it

AI file tools are genuinely useful and genuinely fast. That speed is the reason to prepare. A single confident instruction - “tidy this folder,” “rename these consistently,” “merge the duplicates” - can move, rename, or delete far more than you pictured, and it can do it in seconds. The goal here isn’t to be nervous about that. It’s to make any mistake a quick undo instead of a bad day.

This guide is deliberately tool-agnostic. Whether you’re using ChatGPT Work, Claude Cowork, or something else, the protection layer sits underneath the tool, so the same setup carries across whatever you use next.

The five ways, at a glance

Each of the sections below covers one approach, with what it’s good at, where it falls short, and who it’s best for:

• Manually duplicating the folder
• Time Machine
• Cloud-drive version history (iCloud, Dropbox, Google Drive, OneDrive)
• Git
• CoworkRestore (automatic local version history)

None of these are “the wrong choice.” They solve different sizes of problem, and the last section is about combining them rather than picking a single winner.

1. Manually duplicating the folder

The oldest trick there is: select the folder in Finder, press Cmd‑D, and let macOS make a full copy sitting right next to the original. Now you have a frozen “before” version. If the AI makes a mess, you delete the messed-up folder and rename the copy back.

Pros.It needs no setup, no app, and no account. It works on any Mac, offline, and you can see exactly what you copied. For a one-off task on a single folder, it’s hard to beat for simplicity.

Cons. It only helps if you remember to do it every single time, which in practice means most of the time you won’t. The copy lives on the same disk, so it doesn’t protect against a disk failure. It captures one moment - if the AI runs several tasks, you only have the state from before the first copy, not before each change. And a stack of Project copy 2 folders gets confusing fast.

Best for.A single, deliberate task on one important folder, when you want zero setup and you’ll remember to do it this once.

2. Time Machine

Time Machine is Apple’s built-in backup. Point it at an external drive (or a network location) and it quietly saves versions of your whole Mac, roughly every hour, keeping older copies as space allows. You browse back through time in Finder and restore what you need.

Pros.It covers your entire disk, not just the folder you were thinking about, so it saves you from mistakes you didn’t anticipate. It’s built into macOS, it’s reliable, and it keeps a real history you can step through. Everyone should have a backup like this running regardless of AI.

Cons. The timing is the catch for this specific job. Backups happen about once an hour, so if an AI changes a file and you catch it fifteen minutes later, the good version might never have made it into a backup. It restores by browsing points in time, not by showing you a tidy list of which files one task touched, so pinpointing a single bad edit takes patience. And it needs a backup drive connected - without one, macOS keeps only limited local snapshots for about a day.

Best for.Everyone, as the broad safety net underneath everything else. It’s the backup, not the fast undo.

3. Cloud-drive version history (iCloud, Dropbox, Google Drive, OneDrive)

If your folder lives inside a synced cloud drive, that service is already keeping a history for you. All four - iCloud Drive, Dropbox, Google Drive, OneDrive - keep earlier versions of files and a record of deletions, typically for at least 30 days, longer on paid plans. You restore an older version or an undo of a deletion from the service’s website.

Pros.It’s off-site, so it survives a lost or broken Mac - the one thing local copies can’t do. If you already keep work in one of these, the protection is on by default with nothing extra to install. Deleted files and old versions are usually a few clicks away in the web app.

Cons.Sync can work against you here. When an AI tool walks a folder quickly, the sync client is racing to keep up, and version history for a rapid burst of changes can be patchy. There’s a specific trap on iCloud Drive: with Optimize Mac Storageturned on, macOS can replace files you haven’t opened recently with placeholder stubs, and a tool that reads those stubs as empty can end up copying empty files. Restoring is also per-file through a web interface rather than a clean “show me everything this task changed” view. Our recovery guide for deleted files covers the cloud-history steps in more detail.

Best for.People whose work already lives in a synced cloud drive and who want an off-site copy without thinking about it. Keep it, but don’t rely on it as your only undo for fast AI edits.

4. Git

Git is the version-control system developers use. It records the state of a folder every time you tell it to, keeps a complete history, and lets you return to any saved point precisely. It’s the gold standard for tracking changes to a set of files.

Pros.Its history is exact and detailed. You can see precisely what changed between any two saved states, return to any one of them, and it handles large, complex folders without breaking a sweat. If you already work this way, it’s an excellent safety net and you don’t need anything else for the versioning job.

Cons.It was built for programmers, and it shows. It runs from a terminal, it uses vocabulary that takes real time to learn, and it expects you to save each version by hand - which brings back the same “did I remember?” problem as manual copies. For a marketer, writer, analyst, or researcher who just wants their files kept safe, the learning curve is steep and out of proportion to the task. It’s a fantastic tool aimed at a different audience.

Best for.People who already know it, or who are genuinely willing to learn a developer workflow. If that’s not you, that’s completely fine - the next option gives you the same “return to an earlier version” safety without any of it.

5. CoworkRestore (automatic local version history)

CoworkRestore is a Mac menu-bar app built for exactly this moment. You add the folders you care about once, and from then on it automatically saves a version of each one as changes settle - before and around the tasks an AI runs. When something looks wrong, you open the folder’s history, see a plain list of which files were added, changed, or deleted, and put back a single file or the whole folder. Every restore takes a safety copy first, so an undo is itself undoable.

Pros.It’s automatic, so there’s no “did I remember to save a copy?” It gives you the one thing the other options make hard: a readable, per-task list of what changed, and one-click restore of just the files you want back rather than all-or-nothing. It needs no terminal and no developer knowledge, and it works alongside whatever tool made the changes - ChatGPT Work, Claude Cowork, or another - because it watches the folder, not the tool. For ChatGPT Work specifically, that connection is automatic folder watching; there’s no ChatGPT extension or native integration to set up.

Cons - and these matter. It is nota complete backup strategy, and you shouldn’t use it as one. It keeps version history for the specific folders you add, stored locally on your own Mac. It is not an off-site or cloud backup, so it can’t help if the Mac itself is lost, stolen, or its disk fails - that’s what Time Machine and a cloud copy are for. It only recovers what it actually captured: nothing from before it was installed, from a folder you hadn’t added, or from a moment the project was paused. And it’s Mac-only - Apple Silicon, macOS 13 or later.

Best for. Anyone who regularly hands folders to AI tools and wants a fast, no-jargon undo layered on top of a real backup. You can start with one protected folder for free and add more as you go.

Which should you use?

The honest answer is that this isn’t an either/or. The approaches above solve two different problems, and the calm setup uses one from each group:

• A real backup, for the “my Mac is gone” scenario. Time Machine to an external drive, plus a cloud copy of your important folders. This is your floor. It protects the whole disk and it survives hardware failure and theft. Nothing else in this guide replaces it.
• Automatic version history, for the “the AI just changed the wrong thing” scenario. Something that captures around each task and lets you review and roll back a single file quickly. CoworkRestore is built for this; Git does the same job if you already live in it.

If you only do one thing today, make sure you have a real backup running - that’s the layer you can’t recreate after the fact. Then add automatic version history so the everyday AI mistakes become a five-minute fix instead of a Time Machine expedition. For a fuller walkthrough of running an AI cleanup safely from start to finish, see how to let AI organize your files without losing control.