What is the most important item on the Claude Code safety checklist?

Turn on an automatic backup for wherever your project lives (Time Machine on Mac, File History on Windows, or a cloud-synced folder like Dropbox, Google Drive, or iCloud). It runs without you remembering anything, and it is the layer that saved people in the worst real cases. Everything else on the list closes a smaller, more specific gap on top of it.

Do I need to change any settings to use Claude Code safely?

Mostly no, and that is the good news. By default Claude Code starts with read-only permissions and asks you before it edits a file or runs a command that changes anything, and it can only write inside the folder where you started it. The safe move for a beginner is to keep those defaults, not to change them. The risk starts when you switch on a mode that auto-approves actions before you have a backup in place.

Isn't Claude's /rewind enough to undo mistakes?

No, and this is the gap most people learn the hard way. /rewind only undoes Claude's own Write and Edit edits inside the current session. It does not undo files removed through terminal commands like rm or mv, and it does not cover untracked files like your .env or a local database. Treat it as a fast everyday undo, not a safety net, and put a real backup under the files it cannot see.

Can Claude Code delete files outside my project folder?

Not without explicit permission. Anthropic's security docs state that write operations are confined to the folder where Claude Code was started and its subfolders, so it cannot modify files in parent directories on its own. That is exactly why giving it a dedicated folder (never your Desktop or home directory) keeps the blast radius of any mistake small.

Jul 6, 2026

The Claude Code Safety Checklist (Do This Before Your First Session)

A plain-English Claude Code safety checklist a beginner can finish in a few minutes: keep the default permission prompts, scope it to one folder, turn on a backup, set a git checkpoint, and cover the files /rewind and git quietly miss. Do-this-today steps, no jargon.

You are about to let an AI make real changes to the real files on your computer. Before your first session, run this Claude Code safety checklist. It is short, it is plain English, and a beginner can finish the core of it in a few minutes. No coding required, and most of it is free because it uses tools you already have.

The goal is simple: make any mistake recoverable instead of catastrophic. Do these in order. Each step closes a gap the one before it leaves open.

1. Start in a throwaway practice folder

Your very first sessions should happen somewhere a mistake costs nothing. Make an empty folder called practice, start Claude Code inside it, and poke around there while you learn what the prompts feel like. When you are comfortable, move to real work. This one habit removes the scariest version of every beginner story.

2. Keep the default permission prompts (do not turn them off)

By default, Claude Code starts with read-only permissions. When it wants to do anything that changes your system (edit a file, run a command), it stops and asks you first. A few harmless read-only commands like ls and git status run without asking. Everything else waits for your yes.

That default is your seatbelt. Keep it on while you learn. The unsafe move is switching on a mode that auto-approves actions before you have a backup in place. The popular accept-edits mode, for example, auto-approves file edits plus a fixed set of filesystem commands including rm, mv, and cp inside your project (we broke this down in is it safe to let Claude Code auto-accept edits?). Speed modes come later, after your net is up.

And actually read the prompts. After twenty of them it is tempting to hit yes on autopilot, but a permission prompt only protects you when you look at what it is asking.

3. Give it a dedicated folder, never your Desktop or home directory

Per Anthropic's security docs, Claude Code can only write to the folder where you started it and its subfolders. It cannot modify files in parent directories without explicit permission. That boundary is real, so use it: start each project in its own dedicated folder.

Never run it with the working directory set to your Desktop or your home folder. If something goes wrong there, the blast radius is everything you own. Inside a dedicated project folder, the worst case is that one folder, which the earlier steps make recoverable anyway.

4. Turn on an automatic backup

This is the single highest-value step, because it runs without you remembering anything.

Mac: turn on Time Machine for wherever your projects live.
Windows: turn on File History.
Either way: keep your project inside Dropbox, Google Drive, OneDrive, or iCloud. They quietly keep version history, so an older copy is usually one right-click away.

A "backup-synced folder" just means a folder some service is automatically keeping copies of. Set it once and forget it. In the worst real cases, an automatic backup is what let people get their work back.

5. Ask Claude to set up git and make a checkpoint

You do not need to learn git. You just need snapshots you can roll back to. Paste this in plain English:

"Set up git for this project if it isn't already, and commit a checkpoint right now so I have a safe point to return to. Do this again before any big change."

Then make it a habit: before you hand Claude a "fix the build," "clean this up," or "reorganize these files" task, ask for a fresh checkpoint first. Those messy tasks are exactly when things go sideways, so a snapshot right before them is cheap insurance.

6. Know what /rewind can and cannot undo

Keep using /rewind (press Esc twice) for quick undos of Claude's direct edits. Just do not mistake it for a safety net.

/rewind only undoes Claude's own Write and Edit edits inside the current session. It does not undo terminal commands like rm or mv, and it does not cover untracked files like your .env or a local database. That blind spot is exactly where the "Claude deleted my work" stories come from. For the full picture of what undo actually covers, see how to undo in Claude Code.

7. Be careful with untrusted content

The newest kind of risk is not the tool going rogue, it is hostile text. A web page or a README inside a project you downloaded can hide instructions aimed at the AI. Claude Code ships defenses for this (sensitive operations still need your approval, and commands that fetch content from the web are not auto-approved by default), but the docs are honest that no system is completely immune.

So the beginner rule is short: stick to projects and pages you trust, do not pipe random internet content into Claude, and keep the permission prompts on when touching anything you did not create. For your own small learning projects, this risk is close to zero.

8. Cover the files git and /rewind both miss

Here is the one gap the steps above leave open. Git protects only what you committed. /rewind protects only Claude's direct edits in one session. So the files that fall through both are your .env (your secret keys), your local database, and brand-new files you have not committed yet. Those are the ones that hurt most when they vanish, because there is no history to restore from.

If you are technical, you can hand-roll PreToolUse hooks to guard specific paths. If you would rather not wire that up per project, a tiny local add-on called Undeletable fills the same gap: it saves a byte-for-byte copy of a file before Claude touches it, whether Claude edits it directly or deletes it with a terminal command. If something goes wrong, you type /restore and get it back, including the .env and the database git and /rewind skip. It runs entirely on your machine (no account, no upload), it is a one-time $19, and it is prevention, not magic: it protects files from the moment you install it, which is the whole reason to set it up now rather than after a scare.

The short version

If you only do one thing today, do step 4 (turn on a backup). If you do three, add the dedicated folder (step 3) and the git checkpoint (step 5). Keep the default prompts on while you learn, know what /rewind cannot see, and cover the files it misses. Stacked together, "Claude Code deleted my work" goes from a catastrophe to an annoyance you fix in one command.

Get the checklist in your inbox

Want this whole list in a calm, do-this-then-this format you can keep? Grab the free Claude Code Safety Checklist. It is one email, the checklist, done: no jargon, no spam, and it is sitting in your inbox the day you need it.

Already had the scare and landed here looking for recovery? Start with Claude Code deleted my files: how to recover them. And if you are still deciding whether to try it at all, here is the honest answer on whether Claude Code is safe.

Frequently asked questions

What is the most important item on the Claude Code safety checklist?: Turn on an automatic backup for wherever your project lives (Time Machine on Mac, File History on Windows, or a cloud-synced folder like Dropbox, Google Drive, or iCloud). It runs without you remembering anything, and it is the layer that saved people in the worst real cases. Everything else on the list closes a smaller, more specific gap on top of it.
Do I need to change any settings to use Claude Code safely?: Mostly no, and that is the good news. By default Claude Code starts with read-only permissions and asks you before it edits a file or runs a command that changes anything, and it can only write inside the folder where you started it. The safe move for a beginner is to keep those defaults, not to change them. The risk starts when you switch on a mode that auto-approves actions before you have a backup in place.
Isn't Claude's /rewind enough to undo mistakes?: No, and this is the gap most people learn the hard way. /rewind only undoes Claude's own Write and Edit edits inside the current session. It does not undo files removed through terminal commands like rm or mv, and it does not cover untracked files like your .env or a local database. Treat it as a fast everyday undo, not a safety net, and put a real backup under the files it cannot see.
Can Claude Code delete files outside my project folder?: Not without explicit permission. Anthropic's security docs state that write operations are confined to the folder where Claude Code was started and its subfolders, so it cannot modify files in parent directories on its own. That is exactly why giving it a dedicated folder (never your Desktop or home directory) keeps the blast radius of any mistake small.
How long does this safety setup take?: A few minutes for the core steps, about ten if you do all of them. None of it requires coding, and most of it is free because it uses tools you already have on your computer. The free checklist at guima.ai/safety walks you through it in the right order.

Safety checklist · free

Never lose your work to Claude Code.

Drop your email. The free Claude Code Safety Checklist lands in your inbox. The 2-minute setup that stops almost every “Claude deleted my work” story.

free · one email · the checklist · unsubscribe anytime