Understanding Permission Modes: Default, Accept Edits, Plan Mode, Bypass
Understanding Permission Modes: Default, Accept Edits, Plan Mode, Bypass
~7 Min. Lesezeit Zuletzt aktualisiert am August 8, 2026
The last chapter showed that Claude Code asks for confirmation by default before changing files or running commands. Exactly how that confirmation behaves can be controlled through different permission modes. This chapter introduces the most important ones and explains when each makes sense - and what risks come with each.
Default mode: ask before every action
In default mode, Claude Code asks for your confirmation individually before every file change and every command run through the Bash tool. This is the safest mode and the right starting point, especially in a new or unfamiliar project: you see every planned action before it happens, and can reject it or ask for adjustments.
Accept edits: automatically accepting file changes
In accept-edits mode, file changes (Edit and Write) are applied automatically without requiring individual confirmation - commands run through the Bash tool may still require confirmation depending on configuration. This noticeably speeds things up when you're working through a series of smaller, easy-to-follow changes, for example implementing a plan you've already agreed on. You're deliberately giving up some control in exchange for speed.
Plan mode: plan first, act later
In plan mode, Claude Code still reads your project as usual, but makes no changes yet - instead, it works out a concrete plan for how a task should be implemented and presents it to you for review. Only once you approve the plan does the actual implementation begin. This is especially valuable for larger, more complex tasks where several reasonable approaches exist. Block 4 of this series dedicates a full chapter to plan mode.
Bypass mode: (almost) no more prompts
In bypass mode, Claude Code carries out actions largely without asking for confirmation. That can make sense in tightly scoped, well-controlled situations - for example in an isolated test environment where nothing important can break anyway. For everyday work, especially in real projects with real data, this mode should be used with caution.
Achtung: In bypass mode, the safety layer from the last chapter is essentially gone: a misunderstood prompt or an unexpected chain reaction of commands can take effect immediately, with no chance for you to step in beforehand. Only use this mode when you can precisely estimate the impact and any damage would stay limited in the worst case - never carelessly in a production system or with real customer data.
Which mode to use when
- Default: the normal case, especially in new or important projects - maximum control.
- Accept edits: for a series of smaller, clearly understandable changes - a bit more speed, a bit less control over file changes.
- Plan mode: for larger or unclear tasks where an approach should be agreed on first.
- Bypass: only in tightly controlled, low-risk environments, with full awareness of the consequences.
You can switch modes at any point during a running session - so you're not locked into a choice once made. For the rest of this series, especially while building the example project starting in block 3, default mode is the recommended starting point.