Memory write transparency: show file path and diff content
Resolved 💬 3 comments Opened Feb 5, 2026 by seeekr Closed Feb 8, 2026
Problem
When Claude writes to memory, the UI currently shows a collapsed summary like:
Recalled 1 memory, wrote 1 memory (ctrl+o to expand)
This lacks critical information for user oversight:
- Which file was written to — global memory (
~/.claude/CLAUDE.md) vs project memory (./CLAUDE.md) vs other paths are meaningfully different, and Claude sometimes picks the wrong level - What was actually written — the exact diff/content, not just "wrote 1 memory"
Why this matters
Claude isn't perfect at:
- Choosing the right memory file (global vs project-local)
- Formulating memory entries exactly as the user intends
- Understanding what scope a piece of information belongs at
Without seeing the actual write, users can't catch and correct these mistakes in real-time.
Request
Add a configuration option (or make it the default) to show:
- The full file path of each memory file being written
- The diff or content of what's being written
This could be behind a verbose/transparency flag for users who want it, but the information should be accessible without having to manually check files after the fact.
Environment
- Claude Code version: 2.1.31
---
_This issue was created by Claude Code on behalf of @seeekr_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗