After a few sessions, you notice a pattern: you’ve approved “list the files” forty times this week. You’ve approved “show me the changes” thirty. You’ve approved the same harmless read so many times you’re not even looking at it anymore.
That’s a problem. Not because the dialogs are slow — but because when you stop reading the boring ones, you stop reading the important ones too.
What an allowlist is
The fix isn’t to switch to a faster mode and turn off all the asking. It’s to build an allowlist — the set of specific, boring actions Claude may take without asking again. Everything else still stops at the dialog.
You build it one click at a time. Remember the Always allow choice from Lesson 5.2? Every time you click it on a genuinely harmless action, you’ve added that action to your allowlist. That’s all an allowlist is — the running record of the “always” decisions you’ve made.
A good allowlist makes the dialogs you do see impossible to ignore.
Once the constant, harmless reads are on your list, the dialogs that appear are all the ones that actually matter. The signal-to-noise of the whole experience flips.
What belongs
The litmus test: would I have done this myself, without thinking? If yes, it’s a candidate for Always allow. If you’d hesitate even for half a second, click Approve once instead and leave it off the list.
Good candidates — read-only, runs constantly, never changes anything:
- Listing files, showing a file’s contents, searching the project.
- Showing what changed, the history, which branch you’re on.
- Checking a version or a status.
Bad candidates — keep these on the dialog every time:
- Anything that deletes, moves, or overwrites a file that matters.
- Anything that runs your code in a way that could touch real systems or real data.
- Anything that reaches the network — sending, publishing, pushing, fetching from a URL.
- Anything you only learned about yesterday — let it appear in a few dialogs first, until you know it’s safe everywhere you’d hit it.
Control finer than a mode
The whole point is that you have a dial between “ask about everything” (which goes numb) and “ask about nothing” (which is reckless). Each Always allow turns one boring thing off, and leaves everything else on. That’s far safer than switching to a fast mode, because a fast mode drops all the asking at once — the scary actions right along with the boring ones.
Under the hood, that allowlist is a real list Claude keeps. You can read and edit it directly later — that’s a Power Track detail in “Make Claude yours.” For now, clicking Always allow on the right things is all the control you need.
The discipline
Grow the list slowly. One action at a time, after you’ve seen it enough to know it’s safe in every place you’d ever let it happen. Your allowlist is a long-term part of your relationship with Claude — it’s worth a few seconds of thought each time you add to it.
What’s next
The dialogs and your allowlist control what happens inside a project. The next lesson is about a decision that happens earlier than any of them: whether you should be letting Claude into this folder in the first place.