[BUG] Memory files bypass acceptEdits diff confirmation — no user review before write

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When using acceptEdits permission mode, editing files in the project working directory triggers a diff confirmation dialog — the user sees what's about to change and can approve or reject. However, writing to memory files (~/.claude/projects/.../memory/) does not trigger this diff dialog. The write goes through silently with no user review.

This means AI-initiated memory writes have no user-facing confirmation checkpoint, unlike all other file edits under acceptEdits mode.

What Should Happen?

Memory file writes should go through the same diff confirmation dialog as any other file edit under acceptEdits mode. Users should have the opportunity to review and approve/reject memory writes before they happen.

Error Messages/Logs

Steps to Reproduce

To reproduce

Start a session with acceptEdits permission mode
Edit any project file (e.g., a .md file in the working directory) → diff confirmation dialog appears as expected
Have the AI write a memory file (e.g., via the Write tool to ~/.claude/projects/<project>/memory/test.md) → no diff dialog appears, file is written directly

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.119 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Related issues

#47081 (config file permission inconsistencies)
#23341, #23617 (memory subsystem permission gaps)
#58815 (memory write behavior)
#37253, #35718 (~/.claude/ path protection)