Hey IH 👋 I’m excited to introduce CoworkRestore!
I've been using Claude Cowork for lots of small non-coding projects: documents, notes, exports, little experiments, website copy, random folders of work-in-progress files.
In my experience "undo that" is not something Claude can reliably do. I've accepted this for coding projects where Git is set up - I can review the diff, restore files, or roll back.
But for smaller Claude Cowork projects, Git feels like too much - I don't want to interact with Git every time I let Claude touch a random folder.
So I built CoworkRestore https://coworkrestore.com to automatically snapshot project folders before and after Claude works on a task. Pick a project folder and you are done. Changes are reviewable and reversible.
Under the hood, CoworkRestore sets up its own Git repo for the project folder - separate from any Git repo you may already have in that project.
For Claude Cowork, there is a Claude Desktop extension that lets CoworkRestore know when Claude starts and finishes a task, so snapshots can happen automatically.
There is also an MCP server for Claude Code, so Claude Code can do the same thing.
It's mostly for:
non-technical people using Claude Cowork on real files
people working on documents, notes, folders, exports, content, etc.
anyone who wants a simple "what changed?" and "restore this" button
technical people who cannot be bothered to set up Git for every tiny Claude Cowork folder
It's local-only, macOS-only for now, and free for one project.
I've also seen people mention losing files or having Claude make unexpected changes in Cowork. The tool will make that less scary: let Claude work, but keep a reviewable, reversible history of what happened.
Would love feedback, especially from people using Claude Cowork for non-coding work.
How do you currently review and roll back Claude Cowork changes outside of proper coding projects?
Smart idea! Auto-snapshots between AI tasks is exactly the kind of safety net that should exist for this workflow. Exactly as simple as it should be.
What stood out to me wasn't the snapshots—it was recognizing that the friction wasn't rollback itself, it was the fact that Git is overkill for a lot of non-coding workflows.
Sometimes the opportunity isn't replacing an existing tool. It's making people willing to use the capability they were avoiding altogether.
Curious, are the snapshots intended mainly as a safety net for undo/rollback, or do you also see them becoming a lightweight version history that users can browse and restore from?
The entire change history is preserved, and is browsable. That is the secondary use case.
Quick review / undo of last changes made by Claude is the main use case.