Claude rolls out unified memory across Chat and Cowork
Claude has introduced a single shared memory layer spanning Claude Chat and Claude Cowork, with users deciding what is retained. In a post on X, Claude said handing Cowork a task now starts from what the system already knows from chats, including projects discussed, a manager's preferences, or a client from last quarter. The rollout also adds a dedicated Memory tab, splits stored topics into separate categories, and introduces a Settings toggle for keeping memories about sensitive subjects. For operators and builders, the move reduces re-explaining context when moving between chat and delegated work. The announcement does not specify retention duration, export paths, or admin enforcement, so compliance teams still lack concrete policy hooks.
Claude rolls out unified memory across Chat and Cowork
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 Cowork can now start delegated tasks with context already learned in chat, cutting repeated setup for projects, preferences, and clients.
What happened
Claude announced unified memory across Claude Chat and Claude Cowork in a post on X, stating users decide what the system keeps in memory.
The same announcement says Cowork tasks can begin from prior chat context such as discussed projects, a manager's preferences, or a client from last quarter, and related notes cite a Memory tab, categorized topics, and a sensitive-topics toggle in Settings.
Evidence
Claude now uses one shared memory across Chat and Cowork.
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 learned in 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.
Memory management now includes a dedicated tab and categorized topics.
X · attributed
Memory now has a dedicated tab in Claude
Users can control retention of sensitive-topic memories via Settings.
X · attributed
a new toggle to keep memories about sensitive topics has been added to the Settings menu.
Why it matters
Linking chat and Cowork memory increases continuity for agentic work, but also concentrates personal and workplace context in one store that users must actively curate.
Limits and uncertainties
The packet does not state retention duration, deletion workflows, export options, or enterprise admin controls for unified memory.
Practical implications
Teams using Claude Chat and Cowork should review the Memory tab, topic categories, and sensitive-topic toggle before relying on cross-surface context in production workflows.
What to watch
Whether Claude publishes detailed memory retention, deletion, and enterprise governance rules beyond the initial X announcement.
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
