Plan mode defaults to .claude/plans/ which is a protected path — every edit prompts for approval

Bug

Plan mode saves plans to ~/.claude/plans/ (or .claude/plans/ inside a repo) by default. The permission system hardcodes .claude/ as a protected directory that always requires user approval for edits, regardless of the permission mode setting (including acceptEdits).

This means every single edit to a plan file triggers an approval prompt, even when the user has explicitly configured auto-accept for edits. During a session that involves dozens of edits to a plan file (e.g., updating architecture decisions across a large plan), this makes the workflow extremely frustrating.

Steps to Reproduce

1. Set permission mode to acceptEdits (auto-accept edits)
2. Enter plan mode (/plan or EnterPlanMode)
3. Plan mode creates a file at ~/.claude/plans/<name>.md
4. Every Edit tool call to that file prompts for user approval
5. Same issue with plans stored in <repo>/.claude/plans/ per project conventions

Expected Behavior

Either:

• Option A: .claude/plans/ should not be a protected path (plans are user-facing working documents, not sensitive config)
• Option B: Plan mode should save to an unprotected location by default
• Option C: The plan file path assigned by plan mode should be automatically whitelisted for the duration of the session

Environment

• Claude Code VS Code extension
• Permission mode: acceptEdits
• macOS (Darwin 25.3.0)
• Model: Claude Opus 4.6

Impact

Any session that iteratively builds or updates a plan becomes a wall of approval prompts. The tool creates the file in a location it then refuses to write to without permission — the system is fighting itself.