Claude Memory Freshness Log

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.

2026-07-06 Phase 2 tool check

Phase 2 added browser-only tools and rechecked the memory behavior used by those tools. Current Claude Code docs state that auto memory is on by default, requires Claude Code v2.1.59 or later, stores project memory under ~/.claude/projects/<project>/memory/ by default, shares that directory across worktrees in the same git repo, and loads the first 200 lines or 25KB of MEMORY.md at session start.

The setup and context-budget tools also rechecked Claude Help Center memory behavior: app memory uses an editable summary, project memory spaces are separate from non-project chats, incognito chats do not contribute to memory or chat history, and memory updates within 24 hours after conversations are created, modified, or deleted.

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.