Your first few conversations with Claude Code will hit a moment that feels like a record scratch: it stops, mid-task, and a panel slides in asking you a question.
Before doing anything that changes your files or runs something on your computer, Claude pauses and asks. You click to allow it or not.
That pause is the permission prompt. It’s the most important safety feature in the whole app. It’s also the thing people are most tempted to switch off. Don’t.
What you’ll see
You ask Claude to do something — say, “delete the empty README.” Instead of just doing it, a small panel appears in the app showing:
- What Claude wants to do — the exact change or action.
- Where — which file or folder it affects.
- Your choices — buttons to allow it once, allow it from now on, or decline.
You click. Claude waits. This is the app’s Ask permissions mode, and for everything in this course, it stays on.
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 from now on for this kind of action. Skip the prompt for similar things in the future. Use this only for actions you’d cheerfully do yourself without thinking — like reading a file.
- Decline. 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.
- “Allow from now on” is a one-way door — each one removes a future chance to catch a mistake.
Try the decisions yourself
Here’s the judgment in miniature: a run of permission asks, each one a real choice. Decide allow or decline, and watch the blast radius of each call — how much could go wrong if you get it wrong.
Why this is good, not annoying
Claude makes mistakes. It can be confidently wrong — wrong file, wrong folder, wrong action. 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 happen.
The deep version of this — permission modes, settings, when to widen the gate — is its own level (Level 5 — Trust & safety, coming up). For now: read the panel, click “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.