Claude Code permissions and plan mode

Claude Code permission prompts, auto-accept edits and plan mode: when to use each, how Shift+Tab switches between them, and how to stay safe.

Lesson 2.3โฑ 7 min read๐Ÿšฒ Getting goingโ“ 3-question quiz
The short answer

Claude Code asks permission before editing files or running commands. Press Shift+Tab to cycle between normal mode, auto-accept edits and plan mode, where Claude researches and proposes a plan without changing anything.

Why permissions matter

By default Claude Code is cautious: reading files is fine, but editing files and running commands require your approval. When it asks, you can usually:

  • Allow once
  • Allow and don't ask again for this kind of action (for this session or project)
  • Decline and tell Claude what to do instead

You can review and manage saved rules with the /permissions command.

The three everyday modes

Press Shift + Tab to cycle through modes. The current mode shows at the bottom of the screen.

  • Normal (labelled Manual on screen): asks before each edit or command. Best when learning or in sensitive code.
  • Auto-accept edits: file edits go through without prompts (commands may still ask). Great for flow once you trust the direction.
  • Plan mode: Claude can read and research but cannot change anything. It produces a plan for you to approve.
Analogy: plan mode is the architect's drawing; normal mode is building brick by brick with an inspector; auto-accept is letting the trusted crew crack on.

When to use plan mode

Use plan mode when:

  • The change touches many files (e.g. migrating a library across 30 files).
  • There are several valid approaches and you want to choose.
  • Architecture decisions are involved.
  • You're new to the codebase.

Skip it for small, well-understood fixes (a single-function bug with a clear error message). A common pro pattern: plan mode to investigate and design, then normal or auto-accept to implement.

Staying safe

Careful with "skip all permissions". A flag like --dangerously-skip-permissions exists for isolated, throwaway environments such as sandboxed containers. Never use it on your main machine with access to important files or credentials.
  • Commit your work to git before big changes so you can roll back.
  • Keep secrets (API keys, passwords) out of files Claude reads, or deny access to them in settings.
  • Read commands before approving them, especially anything that deletes or deploys.

Check yourself

Three quick questions to check it stuck.

Ask the tutor

Stuck on something in this lesson? Ask the AI tutor. It answers from this lesson and points you to others that help. Answers are written by AI and can be wrong. Do not include personal details, passwords or company secrets.

Frequently asked

How do I turn on plan mode in Claude Code?

Press Shift+Tab to cycle modes until plan mode is shown at the bottom of the screen. In plan mode Claude researches and proposes a plan without editing files.

How do I stop Claude Code asking for permission every time?

Choose the "don't ask again" option when prompted, switch to auto-accept edits with Shift+Tab, or add allow rules in your settings.json permissions.

Is it safe to skip permissions in Claude Code?

Only in isolated, disposable environments like a sandboxed container. On your normal computer keep permissions on and review commands before approving them.