Claude proposes, you approve

You’ve already met the permission prompt. Back in Lesson 2.6 it appeared the first time Claude wanted to change a file. Now it’s the whole point of a level.

Claude proposes. You approve. Then Claude does. That loop is the contract behind everything else in this course.

For your first few sessions, the prompts felt like interruptions. By the end of this level, they’ll feel like the steering wheel they’ve always been.

When you get a prompt — and when you don’t

The dividing line is action, not difficulty.

Claude can read a hundred files without ever asking. It can think for two minutes and write a wall of explanation. None of that needs a prompt — nothing in the world changed.

But the moment Claude wants to do something — edit a file, run a command, hit the network — the loop pauses and asks. The pause is where you decide whether the proposed action matches what you actually wanted.

The friction is the feature

There’s a tempting story that says: “I trust Claude, the prompts slow me down, turn them off.”

That story is wrong in a specific way. The prompts don’t slow Claude down — Claude is fine waiting. They slow you down at exactly the moment your attention is worth the most: just before something irreversible.

Every shipped engineer has a story about a script that did exactly what they told it to, on exactly the wrong directory. The permission prompt is the gap where you spot that before it happens.

This level is a tour of the prompt — how to read it, what your real options are, when to widen the gate, and what to do when you approve something you shouldn’t have. By the end you won’t be tolerating the prompt. You’ll be using it.

What’s next

You’ve seen the loop. Now the prompt itself — what it tells you, and the three buttons that almost everyone misreads on day one.