When Claude asks for permission

Your first few conversations with Claude Code will hit a moment that feels like a record scratch: it stops, mid-response, and asks you a question.

Before doing anything that changes your files or runs a command on your system, Claude pauses and asks. You decide whether to allow it.

That pause is the permission prompt. It’s the most important safety feature in the whole program. It’s also the thing people are most tempted to disable. Don’t.

What you’ll see

You ask Claude to do something — say, “delete the empty README.” Instead of doing it, you see a small panel pop into the terminal asking whether to allow the action. The panel shows:

What Claude wants to do — the exact command or file change.
Where — the file path or working directory.
How long to allow it — once, always for this kind of thing, or never.

You pick. Claude waits.

Three answers, three blast radii

Allow once. Just this one time. Next time the same thing comes up, you’ll be asked again. Safe default — use this until you’ve built a feel for what matters.
Allow always for this kind of action. Skip the prompt for similar things in the future. Use this only for actions you’d cheerfully run yourself without thinking — like reading a file.
Deny. Don’t do it. Tell Claude what to do differently.

For now, prefer “allow once.” Two reasons:

You’re new. You haven’t yet built the gut feel for which actions matter and which don’t.
“Always allow” is a one-way door — each one removes a future chance to catch a mistake.

Why this is good, not annoying

Claude makes mistakes. It can be confidently wrong — wrong file, wrong directory, wrong command. The permission prompt is the gap where you catch those mistakes before they happen, not after.

The annoying flavor of safety is the kind that doesn’t prevent anything. The permission prompt prevents real damage every day, for people who actually read what’s about to run.

The deep version of this — permission modes, settings, when to widen the gate — is its own level (Level 6 — Trust & safety, coming up). For now: read the prompt, pick “allow once,” move on.

What’s next

Permission prompts catch Claude when it’s about to do something wrong. But Claude can also be wrong in what it says. The next lesson is the honest part: where Claude falls down.