{"slug": "claude-memory-now-follows-you-into-cowork-heres-how-to-turn-it-off", "title": "Claude Memory Now Follows You Into Cowork — Here’s How to Turn It Off", "summary": "Anthropic on Aug. 25 extended Claude's memory to Cowork, allowing information learned in Chat to carry into Cowork tasks and vice versa, with memory enabled by default for Free, Pro, and Max users. Users can pause or reset memory, edit individual memories, and keep sensitive topics excluded, but cannot keep memory active in Chat while preventing Cowork from using it. The change raises privacy concerns as persistent memory can surface information in later tasks even when users did not deliberately share the original conversation.", "body_md": "Claude’s memory no longer stops at the chat window. Anthropic on Aug. 25 extended the same memory used in Claude Chat to Cowork, allowing information learned in one experience to carry into the other.\n\nUsers can pause or erase Claude’s memory, edit individual memories and keep sensitive topics excluded. They cannot, however, keep memory active in Chat while separately preventing Cowork from using it.\n\n**Claude memory now crosses into Cowork**\n\nIn its [Aug. 25 memory announcement](https://claude.com/blog/claudes-memory-works-everywhere-and-you-decide-whats-in-it), Anthropic said information remembered from chats can inform Cowork tasks, while context generated during Cowork work can carry back into Chat. Claude now saves individual memory topics as conversations happen rather than relying only on summaries created afterward.\n\nThose memories can include projects, working preferences and people mentioned in conversations. The change extends Anthropic’s broader push to place Claude inside everyday workplace tools, including [Claude agents operating inside Slack](https://www.techrepublic.com/article/news-anthropic-claude-tag-ai-agent-slack/) with access to approved conversations, tools and organizational data.\n\nMemory is enabled by default for Free, Pro and Max users. Claude Code remains separate from the Chat-Cowork memory system for now, Anthropic [told The Register](https://www.theregister.com/ai-and-ml/2026/08/25/claude-and-cowork-now-share-what-they-know-about-you/5292412/), which also reported that there is no setting to keep Chat and Cowork memories separate on the same account while memory remains enabled.\n\nPersistent memory can surface information in later tasks even when a user did not deliberately share the original conversation. In July, [shared Claude chats appeared in Google Search](https://www.techrepublic.com/article/news-claude-shared-chats-google-search/), showing how information can move beyond the context users expected.\n\n**Pause, reset or narrow what Claude remembers**\n\nOpen **Settings > Memory** and switch off **Generate memory from chats**. Claude then gives users two choices:\n\n**Pause memory:** Existing memories remain stored, but Claude stops using them and creating new ones.**Reset memory:** Claude permanently deletes stored memories, including project memories. The action cannot be undone.\n\nUsers who want more selective control can open **Settings > Memory > Topics** to edit or delete individual memories. **Include sensitive topics in memory** is off by default, preventing Claude from saving categories such as health, race, ethnicity, religious beliefs, politics and gender identity unless the user opts in.\n\nSaved memory is separate from **Search and reference chats**, which can retrieve information from previous conversations and has its own setting. Users trying to reduce how much historical context Claude can access should review both controls.\n\nFor conversations that should remain outside Claude’s ongoing context, [Incognito chats](https://support.claude.com/en/articles/12260368-use-incognito-chats) do not use existing memory or add new memories. Anthropic still retains those chats for 30 days by default, and Enterprise retention policies can extend that period.\n\nPersistent context also adds another variable when agents can act through connected systems. A recent [Claude Opus 4.6 API experiment](https://www.techrepublic.com/article/news-claude-gym-api-flaw/) showed how weak backend controls can let an agent operate beyond restrictions presented in an interface, making both access and retained context relevant when organizations decide where agents belong.\n\n**Read more: For a broader look at enterprise oversight, a ****Claude Code espionage campaign exposed governance gaps around AI agents**** connected to tools and operational data.**", "url": "https://wpnews.pro/news/claude-memory-now-follows-you-into-cowork-heres-how-to-turn-it-off", "canonical_source": "https://www.techrepublic.com/article/news-turn-off-claude-memory/", "published_at": "2026-08-28 11:36:22+00:00", "updated_at": "2026-08-28 13:20:20.399185+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-products", "ai-ethics"], "entities": ["Anthropic", "Claude", "Cowork", "Claude Code", "Slack", "Google Search", "The Register", "Claude Opus 4.6"], "alternates": {"html": "https://wpnews.pro/news/claude-memory-now-follows-you-into-cowork-heres-how-to-turn-it-off", "markdown": "https://wpnews.pro/news/claude-memory-now-follows-you-into-cowork-heres-how-to-turn-it-off.md", "text": "https://wpnews.pro/news/claude-memory-now-follows-you-into-cowork-heres-how-to-turn-it-off.txt", "jsonld": "https://wpnews.pro/news/claude-memory-now-follows-you-into-cowork-heres-how-to-turn-it-off.jsonld"}}