All guidesRecovery guide

Claude Cowork organized my folder wrong — how do I undo it?

When a Cowork cleanup moves, renames, or groups the wrong files — what's recoverable, and how to roll the folder back.

Updated June 13, 2026

The short version

If CoworkRestore was already watching the folder when the cleanup ran, you have two one-click ways out. Open the snapshot from before the cleanup and either rewind the whole folder to that moment, or restore just the files Cowork moved or renamed the wrong way. The good edits stay.

And if the restore itself was the wrong call, Undo last restore brings the cleanup back. Nothing you do here is one-way.

The folders this usually happens in

Bulk organize tasks tend to land on the same handful of folders: the Desktop, Downloads, a screenshots dump, a research folder full of PDFs, a client folder, or whatever document drop has gotten out of hand. You asked Cowork to sort them into subfolders, rename them sensibly, or group them by date or project — and it overreached.

For any of these to be recoverable through CoworkRestore, the folder had to be enrolled in CoworkRestore before Cowork started moving things. CoworkRestore can’t reach back into a folder it wasn’t watching.

Step 1: open the snapshot from before the cleanup ran

Click the CoworkRestore icon in your Mac’s menu bar and select the folder Cowork organized. You’ll see its save points in reverse chronological order, each tagged with what triggered it:

  • claude— Cowork pinged CoworkRestore before or after a task. This is the one you want.
  • auto— the filesystem watcher caught a change on its own.
  • manual— a save point you took by hand.

Find the claude save point with a timestamp just before the cleanup. That’s your “before” picture.

Step 2: read the list of changed files

Open the snapshot. You’ll get a flat list of every file that differs between then and now, marked added, modified, or deleted. Two things to know before you scan it:

  • A rename shows up as one deleted file at the old path and one added file at the new path. Same contents, two rows. Don’t panic at the deletion count.
  • A move into a subfolder reads the same way: the old path is deleted, the new nested path is added.

Click any row to see the file’s contents at the snapshot next to its current state, so you can confirm what actually happened before you touch anything.

Step 3: pick your recovery shape

Two questions decide for you.

Did Cowork get most of it right?

Use per-file restore. On every row that’s wrong — a file moved to the wrong subfolder, a misnamed rename, a screenshot that didn’t belong in the “old invoices” bucket — click Restore this file. It brings that file back to where (and what) it was in the snapshot. If the file didn’t exist at the snapshot, the per-file restore deletes the version Cowork added — which is exactly what you want for undoing a wrong-direction rename: restore the original path, delete the new one.

Every other file stays exactly as Cowork left it. The renames and moves you liked survive.

Did Cowork get most of it wrong?

Use whole-snapshot restore. The entire folder snaps back to the “before the cleanup” state. Faster than picking through dozens of wrong moves one at a time, and the safer call when the structure itself is the mistake.

Step 4: the safety net — Undo last restore

Before any whole-snapshot restore, CoworkRestore takes a safety snapshot of the current state. The Undo last restore button stays available until the next snapshot lands. So if you rewind the folder and then realize Cowork actually did half the job correctly, one click puts the cleanup back and you can switch to per-file mode instead.

Why bulk organize tasks are higher-risk than normal edits

An edit to one document is easy to eyeball. A folder cleanup isn’t. A single “organize my Desktop” prompt can touch hundreds of files, delete from one path and add at another, and reshape the structure in ways that are hard to spot mistakes in while you’re watching it happen. By the time you notice the wrong file ended up in the wrong bucket, the cleanup is done.

That’s why a save point taken just before a cleanup is worth more than one taken before a normal edit — the surface area of what could go wrong is much bigger, and the “list of changed files” view is the only realistic way to audit it after the fact.

What CoworkRestore can and cannot recover

  • Can: roll the whole folder back to any save point, or restore individual files (including deleting files Cowork added at new paths).
  • Can: undo a restore until the next snapshot lands, so a wrong recovery decision isn’t final either.
  • Cannot: recover a folder that wasn’t enrolled in CoworkRestore before the cleanup ran.
  • Cannot: recover changes that happened while the project was paused — there are no save points from that gap.
  • Cannot: recover files matched by the excludes list (defaults skip .DS_Store, build output, and similar noise).
  • Cannot: replace Time Machine or a full-disk backup. It watches the folders you choose, locally, on your Mac.

Make the next cleanup safer

Before you let Cowork loose on the Desktop, Downloads, or a client folder again, run through the short pre-flight checklist in Before you let Claude Cowork organize your Desktop, do this first. It covers folder enrollment, a manual save point, and how to scope the task so a bad cleanup is always recoverable.

For the deeper file-by-file workflow — how to keep the good edits and undo only the bad ones across any kind of Cowork task, not just a cleanup — the hub guide is how to undo bad Claude Cowork file changes.