The Permission Dial — How Much You Let Claude Do on Its Own

Your first build probably came with a little background hum of are you sure? Every time Claude was about to make a file or change one, it stopped and asked. Create this? Edit that? Go ahead? If that felt slightly naggy by the fifth time — good. Because that pause isn't a glitch. It's the whole point. And better still, it's a setting you control.

You're the one driving

Here's the reframe that changes how the rest of this course feels: Claude stops to ask because it's about to touch your files, on your computer. It's checking in before it acts. How often it checks in, though, isn't fixed — it's a dial you turn. Twist it one way and Claude asks before every small step. Twist it the other way and it just gets on with the job and tells you when it's done.

Think of it like handing someone the wheel on a road trip. Sometimes you want them to ask before every turn. Sometimes you know the route is easy and you say, "you've got this — wake me when we're there." Same driver, same car. The only thing that changed is how much you chose to hand over.

The settings on the dial

So what's actually on the dial? A handful of modes. Here they are in the order Claude Code lists them — so the list below matches the menu you'll see on your own screen:

• Ask permissions — Claude does real work, but stops and checks with you before each action. This is usually where you start, and it's what you met during your first build.
• Accept edits — Claude edits files freely without asking each time, but still pauses for the riskier stuff. A bit more trust, a lot less clicking.
• Plan mode — the careful one. Claude reads your folder, thinks, and writes you a plan — but changes nothing. Not one file moves until you say yes. It's looking, not touching.
• Auto mode — Claude runs the whole way through without stopping. It's not unsupervised, though: a separate safety check looks at each action before it happens and blocks anything dangerous. Hands-off, but watched.
• Bypass permissions — Claude skips essentially every check and just does whatever the task needs. This is the one to be careful with — more on it in a moment.

You don't have to memorise these. They live in a little menu right inside Claude Code: in the terminal you flip between them with a quick keyboard shortcut (Shift+Tab), and in the editor or desktop app you click a mode selector. The exact wording shifts a little depending on where you're running Claude — so the only rule worth remembering is read the menu on your screen.

Expand

Plan mode: a beginner's best friend

If you take one thing from this lesson, take this: when you're not sure, start in Plan mode.

In Plan mode, Claude shows you the entire plan before lifting a finger — here's what I'd change, here's the order I'd do it in — and then it waits. Nothing in your folder moves until you read that plan and approve it. It's the closest thing to a "preview before you commit" button, and it's perfect for exactly the moments that make beginners nervous: when you're exploring, when the task feels big, or when you simply don't yet know what Claude will do.

The one to keep switched off: Bypass

Every dial has a far end, and on this one it's called Bypass. In Bypass, Claude stops asking almost entirely and just acts.

Notice that the tool itself tries to talk you out of it. You can't casually flip to Bypass the way you switch the other modes — you have to start Claude up a special way just to enable it, and it will flatly refuse to run in certain setups. That awkwardness is deliberate. People have made real messes letting Claude run wide-open on a machine that mattered.

The rule is short, and you can hold onto it for the whole course: keep Bypass off. The only place it belongs is a throwaway, sandboxed setup where nothing's lost if something goes sideways — and honestly, as a beginner, you may never need it at all.

So which one should I use?

When in doubt: Plan mode, or Ask permissions. Start cautious, watch how Claude handles your kind of work, and nudge the dial up as your trust grows — task by task, not all at once. Keep Bypass off. That's the whole playbook, and it'll carry you a long way.

You can now control how much Claude does on its own. The next win is making sure it does the right thing from the start — so there's less to correct in the first place. The trick is telling Claude about your project up front, in a small file it reads before it does anything. That's where we're headed next.