Short, practical recovery guides for the moments you didn’t plan for — and a setup checklist so the next one doesn’t scare you.
Hub guide: review what Claude Cowork changed, keep the good edits, undo the bad ones — file by file.
Read guideFirst-aid checklist when Claude wipes files: Trash, Finder search, cloud history, Time Machine, editor history — and what to do next.
Read guideCursor's built-in checkpoints come first. Then OS recovery. Then a folder-level safety net for next time.
Read guideWhy /rewind sometimes leaves files behind, and what to check before you assume the work is gone.
Read guideCowork-specific recovery: what to check first, what works if snapshots were running, and what to do if they weren't.
Read guideWhen a Cowork cleanup moves, renames, or groups the wrong files — what's recoverable, and how to roll the folder back.
Read guideBefore you restore anything: see exactly which files Claude Cowork touched and what they looked like before.
Read guideAn unattended Cowork run touched files — here's how to see what changed, recover what you can, and lock down the next one.
Read guideYou don't need to learn Git to be safe. Here's a non-developer setup that gives you the same undo button developers rely on.
Read guideA short pre-flight checklist for any Cowork task that touches a folder you care about — Desktop, Downloads, client work.
Read guide