You’ve already met this moment. Back in Lesson 1.6, the first time Claude wanted to change a file, the app stopped and asked you to approve it. Now that pause is 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, those dialogs felt like interruptions. By the end of this level, they’ll feel like the steering wheel they’ve always been.
When Claude asks — and when it doesn’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 in the chat. None of that needs your approval — nothing in the world changed.
But the moment Claude wants to do something — edit a file, run a command, reach out to the network — the loop pauses and a dialog appears. That 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, these dialogs slow me down, let me turn them off.”
That story is wrong in a specific way. The approval step doesn’t slow Claude down — Claude is fine waiting. It slows you down at exactly the moment your attention is worth the most: just before something irreversible.
Every seasoned professional has a story about a tool that did exactly what they told it to, on exactly the wrong file. The approval dialog is the gap where you spot that before it happens.
This level is a tour of that gap — how to read what Claude is asking, what your real options are, when to widen the door, and what to do when you approve something you shouldn’t have. By the end you won’t be tolerating the approval step. You’ll be using it.
What’s next
You’ve seen the loop. Now the dialog itself — what it tells you, and the choice that almost everyone misreads on day one.