[DOCS] Memory documentation missing last-modified timestamps and freshness reasoning

Open 💬 5 comments Opened Mar 13, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/memory

Section/Topic

The "Auto memory" section describing how memory files work

Current Documentation

The memory page describes auto memory as plain markdown files Claude writes to ~/.claude/projects/<project>/memory/. It explains that MEMORY.md is loaded at the start of every session (first 200 lines), topic files are read on demand, and files are plain markdown users can edit or delete via /memory.

No mention of timestamps, last-modified dates, or freshness reasoning exists on this page.

What's Wrong or Missing?

Changelog v2.1.75 added "last-modified timestamps to memory files, helping Claude reason about which memories are fresh vs. stale." This is a meaningful behavioral change: Claude now uses file modification dates to prioritize newer memories over older ones. A user reading the memory documentation has no way to know that:

  1. Memory files carry last-modified timestamps
  2. Claude uses these timestamps to reason about which memories are current vs. potentially outdated
  3. Editing a memory file updates its timestamp, which affects how Claude weighs it

Suggested Improvement

Add a subsection under "Auto memory" or "How memory works" explaining timestamp behavior:

Suggested addition:

Memory freshness

Memory files include last-modified timestamps. Claude uses these timestamps to reason about which memories are fresh and which may be stale. When memories conflict, more recently modified entries are treated as more current.

Editing a memory file (either directly or through Claude's auto-memory updates) refreshes its timestamp, signaling that the information is current.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/memory | Auto memory section — no mention of timestamps or freshness |

Total scope: 1 page affected

Source: Changelog v2.1.75 — "Added last-modified timestamps to memory files, helping Claude reason about which memories are fresh vs. stale"

View original on GitHub ↗

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