Claude Code Permission Modes
Level 2 · Asking before it acts
The six Claude Code permission modes, from asking about almost every step to asking about none. What each allows, and when to use it.
Course contentsLesson 5 of 16
Level 1 · Starting out
Level 2 · Asking before it acts
Level 3 · Telling it how you work
Level 4 · The tools it uses
Level 5 · Growing past one chat
After this lesson you can
- Name the six permission modes
- Switch modes with Shift+Tab
- Pick a mode for a task and for a script
11 mincovers 8 glossary entries
Worth reading first: Claude Code Prompt Shortcuts
How often Claude Code stops to ask
A permission mode sets how often Claude Code stops to ask before it acts. There are six: Manual, acceptEdits, plan, auto, dontAsk and bypassPermissions. A new session in the terminal starts in auto mode on recent versions. A run with -p starts in Manual. Press Shift+Tab to move between the main modes.
Manual mode asks before almost every step. It reads files without asking, but it stops before it edits a file or runs most commands. Its value in settings is default, and the screen calls it Manual. It suits a project you do not know yet, or work where each step counts.
Accept edits mode lets Claude edit files without asking each time. It also runs common file commands on its own, such as mkdir, touch, mv and cp, inside your project. Other shell commands still need a yes. It fits work you will look over at the end, in git, rather than one change at a time.
Plan mode lets Claude read, search and run commands that only look around, but it does not change your source files. When it is ready, it shows you a plan and waits. You can approve it, change it or ask for more. Then Claude leaves plan mode and starts the work.
Auto mode runs most actions without asking you. A second model checks each action first, in your place. It blocks steps that go past what you asked for, reach systems it does not know, or seem driven by orders hidden in what Claude read. It cuts down prompts, but it is not a promise of safety.
Don't ask mode never stops to ask. Anything that would need a yes is turned down instead, so only what you allowed in advance runs. It is made for scripts and CI jobs, where nobody is there to answer. Bypass mode turns off the prompts and the checks. It is only for a container or a virtual machine with nothing to lose.
Shift+Tab moves from Manual to accept edits to plan, then to bypass and auto where they are switched on. Don't ask mode is never in that loop. You set it, or any mode, when you start: claude --permission-mode plan. The bar under the prompt always shows the mode that is on.
What runs without asking, mode by mode
| Mode | Runs without asking | Best for |
|---|---|---|
| Manual (default) | Reads only | Careful work, a project you do not know |
| acceptEdits | Reads, file edits, common file commands | Changes you review at the end |
| plan | Reads and look-only commands, no edits | Working out an approach first |
| auto | Most things, each checked by a second model | Long tasks with fewer prompts |
| dontAsk | Only what you allowed in advance | Locked-down scripts and CI |
| bypassPermissions | Everything | A throwaway container or VM only |
claude --permission-mode planWorked example
Emma plans first, then lets it run
Emma needs a new export button that touches 6 files she has never read. She starts in plan mode, and Claude comes back with a plan in 5 steps.
She cuts one step and approves the rest. Then she switches to accept edits, and reviews the whole change in git before she commits.
The words for this lesson8
Check yourself
Which mode turns down anything that would need a yes, without asking anyone?
Finished this lesson?
Marking it complete also marks its 8 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.