Freshness surface

Claude Memory Freshness Log

Claude memory features change. This log records source checks and gives future editors a weekly surface to extend.

This site was built from primary sources checked on 2026-07-06.

Future edits should update this page before changing memory availability claims.

Release notes are the first stop for product changes; feature docs are the first stop for behavior details.

Pages should prefer dated statements over timeless claims when availability can drift.

"Release notes" Claude Help Center

2026-07-06 source check

Initial site build. Checked Claude Code memory docs, Claude app memory Help Center article, Projects Help Center article, personalization Help Center article, Project RAG Help Center article, Anthropic context-management post, and Claude release notes.

Editorial decision: state app memory behavior from current support pages, and keep older "Bringing memory to teams" launch framing as product background rather than the latest availability source.

Watch list

  • Memory availability by plan and surface.
  • Settings navigation names.
  • Claude Code auto memory rollout status and default behavior.
  • MEMORY.md startup load limits.
  • Project RAG capacity and retrieval behavior.
  • New controls for export, deletion, enterprise retention, and incognito behavior.

Update procedure

When updating the site, change the source note first, then the affected article, then this freshness log. If a fact comes from a non-primary community source, label it as workflow advice rather than official behavior.

For weekly updates, scan Claude release notes and the memory-related docs. If nothing changed, record "reviewed, no content change" with the date.

FAQ

Why does this site need a freshness log?

Claude memory behavior and availability can change, so dated source checks make claims easier to audit.

What should future editors update first?

Update source notes first, then page content, then the freshness log.

Primary Sources