Anthropic merged the memory systems behind Claude’s chat product and Cowork, its task-running agent, so a fact stated in one now surfaces in the other. The change shipped Tuesday and is on by default for Free, Pro and Max users across web, desktop and mobile, according to the company’s own announcement.
The more consequential shift is timing, not scope. Claude used to hold a fact until a conversation closed, then summarize and store it, which gave a user an implicit last chance to decide nothing there was worth keeping. It now writes topics into memory mid-conversation, so a passing mention that a deadline slipped to September lands in the next session without any explicit instruction to remember it.
That timing change, paired with the merge, means a detail typed into an ordinary chat can steer a Cowork task run on a user’s machine or in the cloud days afterward. Anthropic’s own illustration: point Cowork at a status update for a manager, and it already has that person’s name and writing preferences, pulled from an earlier conversation.
TechCrunch’s Sarah Perez covered the launch and framed the two products as behaving like a single assistant now rather than separate tools that happened to share a brand. The more precise read is narrower: the two products share a memory store, but Claude Code, as this article details below, still does not.
Users keep granular control over what gets kept. Each remembered detail lives as its own file under Topics in the memory settings, and a person can open, edit or delete any single one, with edits propagating across every surface. A separate switch governs whether Claude builds memory from conversations at all, and a second, independent switch governs one narrower category: sensitive topics.
Health, race, ethnicity, religious belief, political affiliation and gender identity are excluded by default even when general memory is running. A user can opt that category in individually; Anthropic’s cited justification is a food allergy shaping recipe suggestions. Flipping the switch does not retroactively store anything discussed before, and going forward Claude flags every save into that category with an on-screen notice.
ZDNET’s David Gewirtz pointed out the tension in that design. Someone working through a sensitive subject repeatedly might experience the recurring flag less as reassurance and more as a reminder they are being tracked.
One boundary holds no matter what a user enables. Social security numbers, government identification, criminal records and immigration status stay outside memory even with the sensitive category switched on.
The account-type split deserves the closest read from anyone buying this for a company. Consumer plans launch with memory active. Team and Enterprise plans do not: an administrator decides whether the organization gets it at all, and each employee then opts in individually rather than inheriting it.
Shifting that call to an admin rather than an individual makes sense given what Cowork already is: not a conversation window but software that executes tasks on a device and in the cloud, and which researchers found in July could be tricked into reading Mac credential files once it broke out of its sandboxed environment. Stacking months of personal context onto a tool with that kind of reach changes the risk calculation in a way a memory-enabled chatbot alone would not. That is likely why the enterprise default landed more cautiously than the consumer one.
Claude Code sits outside this update entirely, an omission Gewirtz says Anthropic confirmed when asked directly, and it is the clearest evidence that the merge is a first step rather than a finished system.
Any team already relying on Cowork, or benchmarking it against the rival Cursor is building, faces a decision that goes beyond the settings toggle itself: before letting an admin apply consumer-style defaults org-wide, determine whether memory the same account may have already built up elsewhere, in a browser panel or a mobile session, needs to sit inside the same compliance boundary a European customer must already document under GDPR.
Reported by Ana Maria Constantin for The Next Web, published August 25, 2026.
