8 min · +100 XP
“Just Build — Don't Ask Me”
The one setting most non-coders actually want.
By the end of this lesson
You'll know how to let Claude run without pestering you — and when to be careful.
By default, Claude Code politely asks permission before each action: 'can I create this file?', 'can I run this?'. If you're a developer, that's useful. If you're not — those questions are just noise you can't really judge anyway.
claude --dangerously-skip-permissions
Run this at the plain terminal prompt (if Claude is already running from before, exit it first — type /exit, or just close and reopen the terminal). The very first time, it shows a warning box asking you to accept the mode — use the arrow keys to pick 'Yes, I accept' and press Enter; you'll see it once. Started this way, Claude stops asking and does the work end to end. This is how a lot of non-developers — and plenty of developers — actually run it.
The word just means 'I won't pause to ask you'. And here's the honest version of why that's fine: Claude works where you point it. Point it at a fresh project folder and that folder IS your sandbox — by convention, not by magic. Keep your projects in their own folders (exactly how this course works) and 'dangerous' mode is just 'don't interrupt me' mode.
Because it won't ask, only point it at your own projects — not at sensitive system folders or anything you'd hate to lose. Nervous? Run plain claude instead and approve each step. Both are fine; pick your comfort.
What does --dangerously-skip-permissions actually do?
Author
Evgeny Arsentyev
PhD · Chief Product Officer at a healthtech company