How to safely use ChatGPT Work with local folders on your Mac

What is on this page

• What ChatGPT Work can actually do to local folders
• Start with a dedicated working folder
• Avoid granting access to your whole Mac
• Test on copies or replaceable material
• State exactly what must not change
• Ask for the plan before any editing
• Keep automatic version snapshots running
• Keep your regular backups too
• Review the changed-file list afterwards
• Use scheduled or unattended tasks carefully

What ChatGPT Work can actually do to local folders

With your permission, ChatGPT Work can open a local folder on your Mac and use the files inside it. When you grant that folder access, it can also create new files, edit existing ones, and rename, move, or organize what is there - depending on the task you give it. The important nuance for safety is that a task can be mostly correct and still change something you meant to keep: a file renamed to match a new scheme you did not want, a stray copy left behind, an original moved somewhere you would not have chosen. That gap between “mostly right” and “exactly what I wanted” is the thing this whole workflow is built to catch.

A note on honesty: these product details are current as of 22 July 2026 and are still rolling out, so treat the specifics as a moving target. If you want the fuller picture of what does and doesn’t reach your local files, the companion page on how CoworkRestore works alongside ChatGPT Work is the place to start.

1. Start with a dedicated working folder

Make one folder that exists only for the work you want ChatGPT Work to do - something like ChatGPT working folder under ~/Projects or ~/Work- and move only the files for this task into it. ChatGPT Work operates there; the rest of your Mac is out of reach. When you are happy with the result, you move the files back yourself. This single habit narrows the blast radius from “everything on my Mac” to “the files I deliberately put in one folder,” and it makes every later step easier.

2. Avoid granting access to your whole home directory

When ChatGPT Work asks for folder access, give it that one working folder - not your home directory, not your Desktop, not your entire Documents folder. The less it can see, the less any task can touch by mistake. If you catch yourself wanting to grant broad access “just in case,” that is usually a sign the job should be split into smaller tasks, each with its own folder. Broad access is the most common way a small mistake turns into a big one.

3. Test on copies or replaceable material first

Before you run a task against files you truly care about, run it once against duplicates. Copy a handful of representative files into the working folder, give ChatGPT Work the same instruction you plan to use for real, and see how it behaves. You will learn whether it interprets your naming rules the way you meant, whether it groups things sensibly, and whether it does anything surprising - all without risking an original. The durable version of this test-small habit is laid out in how to let AI organize your files without losing control.

4. State exactly what must not change

Ambiguous instructions are where AI tasks drift. Before you hand over the task, write down - in the instruction itself - what must stay exactly as it is. Name the files or the rules:

• “Do not rename anything that starts with FINAL_.”
• “Leave the Invoicessubfolder untouched.”
• “Do not delete anything - move it to a folder called Reviewinstead.”

Being explicit about what is off-limits is worth more than describing what you want in general terms. It gives you a clear line to check against afterwards, too.

5. Ask the agent to outline its plan first

Before it touches a single file, ask ChatGPT Work to describe what it intends to do: which files it will change, what it will rename or move, and what it will leave alone. Read that plan. If it says it will delete duplicates and you only wanted them grouped, you catch it now - before anything changes on disk - rather than after. This costs you thirty seconds and is the cheapest place in the whole process to stop a mistake.

6. Keep automatic version snapshots running

This is where CoworkRestore fits, and it is worth being precise about what it is. CoworkRestore is a Mac menu-bar app that watches a folder you add and quietly saves versions of it as changes settle. It works alongside ChatGPT Work through folder watching - there is no ChatGPT extension, plugin, or native integration involved, and it never talks to ChatGPT. It just notices when files in the watched folder change and keeps a reversible version.

Add your working folder to CoworkRestore before you run the task. From then on, if a task changes something you wanted preserved, you can open the version history, see the list of changed files, and restore a single file or roll the whole folder back - without learning Git, the developer tool this kind of “save every version” safety net is usually built on. Two honest limits: CoworkRestore recovers only what it actually captured while watching, so it can’t help with changes from before you added the folder; and it is Apple Silicon only, macOS 13 or later, and local-only. It is one concrete part of the workflow on this page, not a substitute for the rest of it.

7. Keep your regular backups too

Version snapshots and backups are different jobs, and you want both. Snapshots let you undo a specific change inside a watched folder. Backups protect against the bigger failures - a dead drive, a deleted folder, a mistake that predates any snapshot. Keep Time Machine running to an external drive, or keep the folder synced to a cloud service that holds version history (Dropbox, Google Drive, OneDrive, and iCloud Drive all keep deleted files and earlier versions for at least 30 days). CoworkRestore is explicitly not a backup, so don’t retire the ones you already have. The trade-offs between each approach are compared in how to protect a folder before letting ChatGPT or another AI edit it.

8. Review the changed-file list after completion

When ChatGPT Work says it is done, don’t move the results back to their real home yet. The chat summary is a description, not a record of what actually happened on disk. Open your snapshot history and look at the real list of changed files - added, modified, deleted, moved. Most of the time it will match what you expected. Occasionally something will stand out: a delete you didn’t ask for, a rename you wouldn’t have chosen, a file that landed somewhere odd. Catching it now - before the results are mixed back in with your real files - is the difference between a one-click undo and a recovery job. The step-by-step version of this review is in how to see exactly what ChatGPT Work changed in a folder.

9. Use scheduled or unattended tasks carefully

A task you watch run is one you can stop. A scheduled or background task that runs while you are away is not - a wrong turn can compound across many files before you ever see it. That doesn’t mean never use them, but treat them with extra care:

• Point them at a single dedicated folder, never a broad one.
• Make sure version snapshots are on before the schedule fires.
• State clearly what must not change, since you won’t be there to intervene.
• Review the full changed-file list as soon as you are back, before you rely on the results.

The bottom line

Using ChatGPT Work with local folders safely isn’t about one magic setting - it’s a handful of small habits that stack. Give it one folder, keep access narrow, test on copies, say what must not change, read its plan, keep snapshots and backups running, and check the changed-file list before you trust the result. CoworkRestore covers the snapshot piece so any captured change stays reversible; the rest is yours. Set it up once, and after that it takes about a minute per task. If you want the tool-agnostic version of the same discipline, read how to let AI organize your files without losing control.