Claude Code /rewind didn't restore my files — what now?

Why /rewind sometimes “does nothing”

Claude Code’s checkpoint and rewind feature is real and useful, but it has a narrower scope than people assume. A checkpoint records the file edits Claude Code made through its own edit path, within the current session. That leaves a handful of things outside its net — and those are exactly the cases that bring people to a guide like this one.

Common reasons a rewind looks like it failed:

• Wrong session or wrong folder. Checkpoints belong to the session you ran them in. If you opened a fresh terminal, changed directories, or quit and restarted, you’re looking at a different timeline. Re-open the original session, in the original folder, and try /rewind there.
• Earlier checkpoint needed. Rewind goes to the checkpoint you choose, not before it. If the harmful change spans several turns, the right checkpoint may be further back than the one you picked. Run /rewind again and step back another turn or two.
• Changes made by shell commands. When Claude Code runs something through its Bash tool — a build script,rm, mv, a code generator — the effects land on disk without going through the edit path that checkpoints track. Rewind can’t undo those.
• Files deleted outside the agent. If a file disappeared because you, your editor, a formatter, or a watch process removed it, the checkpoint has nothing to put back.
• Edits made before the conversation started. The session can only rewind its own history. Anything that was already broken when you typed your first prompt won’t be fixed by going back to that first checkpoint.
• Folder renames or moves. If the agent renamed or moved a parent folder, the file’s old path may no longer exist where you expect to see it. Search by filename before assuming it’s gone.

A short recovery checklist

Work through these in order. Stop as soon as one of them gets you what you need.

1. Re-run /rewind in the original session and step back further than you did the first time.
2. Check the macOS Trash. Click the Trash icon in the Dock. If a deleted file is there, right-click and choose Put Back.
3. Open Finder’s Recents. The sidebar entry shows every file recently touched on your Mac, sorted by date modified — useful for finding something the agent moved rather than deleted.
4. Spotlight a unique filename or phrase. Press Cmd + Space and type a distinctive word from the missing file. If it still exists anywhere on disk, this finds it.
5. Time Machine, if you have it on. Open the folder in Finder, launch Time Machine, scroll back to before the bad turn, and restore.
6. If you happen to have a git history, the standard recovery moves apply — check your local history and your remote. If “git” means nothing to you, that’s fine. Skip it. We have a separate guide for that case.
7. Ask the same session to re-create the file. If the conversation is still open, the model often still has the contents in context. That’s a re-write, not a restore, but for short files it can be enough.

A safety net that sits outside the session

The reason /rewind has the gaps above is the same reason it’s fast: it’s part of the session. The fix for that, after the dust has settled, is something that watches the folder itself — independent of which tool is editing it, which session is open, or which path the change took to land on disk.

CoworkRestore is a Mac menu-bar app that quietly saves snapshots of any folder you add to it. Point it at the folder Claude Code works in and you get a parallel history that doesn’t care whether a change came from the edit path, a Bash tool, your editor, or a script. When something looks wrong, you open the folder’s history, see which files changed, and restore them one by one without losing the good edits around them.

Plenty of Claude Code users already have version control they trust and don’t need another layer. CoworkRestore is aimed at the rest — people who want a folder-level undo that runs alongside whatever Claude Code is doing internally, without having to think about it.

What to do right now

If you’re still in the broken session, don’t close it until you’ve tried /rewind at an earlier checkpoint and worked through the checklist above. If the file is back, great — now is a good time to set up a safety net so the next bad turn doesn’t cost you the same hour twice.