I don't know Git. How do I safely use Claude Code, Cursor, or Claude Cowork?

Why developers use a safety net — and what yours looks like

When developers let an AI agent edit a folder of files, they almost always have a safety net running in the background. It saves the state of the folder before each change, lists exactly which files were touched, and lets them undo any one of them with a single click. That’s really all it does. The reason it has a reputation for being intimidating is the tooling around it — not the idea.

The non-developer version of the same safety net is just three things: snapshots that happen on their own, a readable list of what changed, and a one-click way to put a file back the way it was. That’s the bar to clear — whether you’re using Claude Cowork to clean up your Desktop, Cursor to draft a website, or Claude Code to refactor a script your team sent you.

What to actually look for in a safety net

Regardless of which AI tool you sit in front of, this is the checklist that matters. Anything that ticks all four boxes will keep you out of trouble.

• Snapshots happen automatically. If you have to remember to save a “before” copy every time, you won’t. The whole point is that your safety net runs whether or not you thought about it.
• You can see what changed before you decide. A plain list of which files were added, modified, or deleted — with a before-and-after view of each one — so you can judge a change instead of guessing.
• You can keep good changes and undo bad ones. Restore should be per-file, not all-or-nothing. The AI usually gets most of a task right; you only want to roll back the one file it broke.
• It survives more than just a clean session. A good safety net keeps working through an editor crash, a folder rename, even a deleted folder — if you store the snapshots in a safer external location instead of inside the folder itself.

Setting this up for Claude Cowork

CoworkRestore is the no-terminal, no-developer-workflow option built specifically for Cowork users. It’s a Mac menu-bar app: you install it, drag the folder you care about into it, and from then on it quietly saves a snapshot before and after every task Claude Cowork runs. When something looks wrong you open the folder’s history, see exactly which files changed, and undo only the bad files while keeping the good edits.

If you’re about to point Cowork at something important — Desktop, Downloads, client work — the pre-flight checklist for organizing your Desktop is a good ten-minute read before you hit go.

Setting this up for Cursor or Claude Code

Both Cursor and Claude Code ship with their own built-in checkpointing. Cursor saves checkpoints inside the editor and exposes them through its chat panel. Claude Code has a /rewind command that walks back recent file changes from inside its session. For most everyday work, those are the right first stop — they’re built in, they don’t need another app, and the people who built them know what their own tool changes.

The honest caveat is that both are tied to the editor that made them. If the session crashes, if you close the project the wrong way, if you rename or move the folder, or if the change happened outside that editor, the in-editor history can come up short. That’s the gap CoworkRestore fills — it watches the folder itself, not the editor, so its snapshots are there whether Cursor or Claude Code remembers them or not. If you want belt and braces, run both: the editor’s built-in checkpointing for instant undos inside a session, plus a folder-level safety net underneath for everything else.

Where snapshots should live

CoworkRestore defaults to storing snapshots inside the folder itself, in a hidden location you never see. That’s the simplest setup and it’s fine for most people. If you’re worried about the AI doing something destructive to the whole folder — renaming it, moving it, or deleting it — switch the storage location to an external folder during setup. Snapshots stored outside the project survive even a whole-folder delete, which is the one scenario where inside-the-folder snapshots can’t help you.

The bottom line

Not knowing Git doesn’t mean working without a safety net. It means picking one that runs at the folder level, configures itself in a couple of clicks, and stays out of your way until the day you need it. Configure it once on the folders that matter — client work, your novel, the launch plan — and forget it’s there. That’s the whole job.