[BUG] CLAUDE.md/memory file edits show "Writing memory" without diff - cannot see what changed
Environment
- Claude CLI version: 2.1.31
- Platform: macOS
- Terminal: Ghostty
Bug Description
When Claude edits CLAUDE.md files (memory files), the UI shows "Writing memory" or "Wrote memory" instead of displaying the actual diff like it does for other files. Even using Ctrl+O to expand verbose output does not reveal what changes were made.
This is a significant transparency issue - users cannot see what Claude is writing to their memory/instruction files without separately opening the file and checking git diff.
Steps to Reproduce
- Ask Claude to add something to CLAUDE.md (e.g., "add a note about X to my CLAUDE.md")
- Observe that the edit shows "Writing memory" instead of the old/new diff
- Press Ctrl+O to expand - still no diff visible
Expected Behavior
CLAUDE.md edits should show the same diff preview as any other file edit, showing:
- The old content being replaced
- The new content being written
- Line numbers and context
Actual Behavior
Shows only "Writing memory" / "Wrote memory" with no visibility into actual changes.
Why This Matters
Memory files contain instructions that affect all future Claude interactions. Users need to:
- Verify Claude understood their intent correctly
- Catch any unwanted additions or modifications
- Maintain control over what instructions they're giving Claude
The diff visibility for regular code files exists for good reason - the same reasoning applies even more strongly to memory/instruction files.
This issue has 12 comments on GitHub. Read the full discussion on GitHub ↗