Should plan mode enforce read-only restrictions when using --dangerously-skip-permissions?

Resolved 💬 3 comments Opened Jan 9, 2026 by nh13 Closed Feb 24, 2026

While in plan mode with --dangerously-skip-permissions, I was able to successfully edit source files using the Edit tool, despite the system prompt clearly stating that edits should be blocked except for the plan file.

I would have expected plan mode to still enforce read-only restrictions regardless of the permissions flag, since plan mode is a workflow feature (for reviewing changes before they're made) rather than a safety permission.

Steps to reproduce:

  1. Start Claude Code with claude --dangerously-skip-permissions
  2. Enter plan mode (user initiated)
  3. Use the Edit tool to modify a source file (not the plan file)
  4. The edit succeeds instead of being rejected

Question:
Is this expected behavior? Should --dangerously-skip-permissions also bypass plan mode restrictions, or should plan mode be enforced independently?

Environment:

  • Claude Code version: 2.1.2
  • Model: claude-opus-4-5-20251101
  • Platform: macOS (Darwin 25.1.0)

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗