Claude Memory Freshness Log

2026-09-19 memory-everywhere source check

Anthropic published "Claude's memory works everywhere, and you decide what's in it". The changes that affect this site:

• Chat memory and Claude Cowork memory are the same memory. Context built in conversation is available when Cowork runs a cloud task, and task context carries back to chat.
• Memory updates as you chat. Claude adds topics during a conversation rather than summarizing it after it ends.
• Memory is a list of topic files. Under Topics in Memory settings, each memory can be read, edited, or deleted individually.
• Sensitive topics are off by default. Health, race, ethnicity, religious beliefs, politics, gender identity, and similar areas are excluded unless the user opts in, and the opt-in is not retroactive. Sensitive ID numbers, criminal history, immigration status, and AUP-violating content stay excluded either way.
• Availability. On by default for Free, Pro, and Max across web, desktop, and mobile. On Team and Enterprise, admins control organization availability and memory is off for individual users until they turn it on.
• The settings path is Settings > Memory, replacing the older Settings > Capabilities wording used across this site.

Editorial decisions from this pass: added memory everywhere as the flagship guide for the change; rewrote the Claude app memory guide around topic files instead of a single after-the-fact summary; retired the "memory updates within 24 hours" timing claim, which described the superseded summary model; and added an explicit note to the Projects guide that the announcement does not restate project-scoped behavior, so the Help Center remains the reference there.

Later the same day, added The Chips, a labeled synthetic topic desk where you can inspect, edit, and delete invented memory files. It is original work by Claude Memories, not a real account. Windows, compaction, and prompt caching remain on claudecontext.com.

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.

Superseded in part by the 2026-09-19 entry above. The summary model and the 24-hour update timing described here were replaced by topic files written during the conversation. The Claude Code auto-memory findings in this entry still stand.

Watch list

• Memory availability by plan and surface, including Team and Enterprise admin controls.
• Whether project-scoped memory keeps a separate summary now that chat memory is stored as topic files.
• Sensitive-topic category list and the always-excluded categories.
• 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.