Claude shares one memory across chat and Cowork with user controls
Claude now shares a single memory layer across standard chat and Claude Cowork, and users decide what context persists between those surfaces. When you hand Cowork a task, it can start from what Claude already knows from your chats—the project you talked through, your manager's preferences, or a client from last quarter—rather than beginning without that history. The update also adds memory governance controls: a Settings toggle to keep memories about sensitive topics, remembered topics split into separate categories, and a dedicated Memory tab in the Claude interface. For operators, the shift tightens integration between conversational chat and agentic Cowork workflows, though the announcement does not spell out retention limits, enterprise policy hooks, or how memory behaves across devices.
Claude shares one memory across chat and Cowork with user controls
Claude now has one memory across chat and Claude Cowork, and you decide what's in it. Hand Cowork a task and it starts from what Claude already knows from your chats: the project you talked through, your manager's preferences, or the client from last quarter.
Key takeaway
Claude Chat and Cowork now draw on one user-controlled memory store, so agentic tasks can reuse prior chat context instead of starting from scratch.
What happened
Claude announced that it now maintains one shared memory across Claude chat and Claude Cowork, with users deciding what is stored. When Cowork receives a task, it can begin from context already established in chats, such as an ongoing project, a manager's preferences, or a client from a prior quarter.
The rollout also expands memory management in the product: a new Settings toggle lets users keep memories about sensitive topics, remembered topics are split into separate categories, and Memory now has a dedicated tab in the Claude interface.
Evidence
Claude now has one unified memory across chat and Cowork with user control over contents.
X · attributed
Claude now has one memory across chat and Claude Cowork, and you decide what's in it.
Cowork tasks can start from context Claude already knows from prior chats.
X · attributed
Hand Cowork a task and it starts from what Claude already knows from your chats: the project you talked through, your manager's preferences, or the client from last quarter.
A Settings toggle was added to keep memories about sensitive topics.
X · attributed
Also, a new toggle to keep memories about sensitive topics has been added to the Settings menu.
Remembered topics are split into separate categories and Memory has a dedicated tab.
X · attributed
Memoriesed topics are now split into separate categories. Memory now has a dedicated tab in Claude
Why it matters
Unifying memory across chat and Cowork reduces context handoff friction and makes agentic workflows more continuous, while new category and sensitive-topic controls shape how much personal context users retain.
Limits and uncertainties
The announcement does not specify retention duration, deletion behavior, or enterprise administration for the shared memory layer.
The packet does not describe how memory sync behaves across devices, accounts, or team workspaces.
Practical implications
Teams using Cowork for delegated work should review what chat context is stored and use the sensitive-topic toggle before relying on cross-surface memory.
Builders integrating Claude workflows should assume Cowork may inherit prior chat facts and design prompts and review steps around user-controlled memory categories.
What to watch
Whether Anthropic publishes documentation on memory retention, export, and enterprise controls for the unified chat-Cowork store.
How users adopt the sensitive-topic toggle and category splits when moving recurring work from chat into Cowork tasks.
Original reporting: Claude now has one memory across chat and Claude Cowork, and you decide what's in it.
Hand Cowork a task and it starts from what Claude already knows from your chats: the project
