Claude's memory now writes while you talk, and it crosses products by default

The end of a conversation used to be a decision point. Claude summarised the exchange after it closed, which meant a user who thought better of the last twenty minutes had somewhere to stand [s1c3]. Mid-conversation writes remove that pause [s1c4]. Capture now happens while the thing is still being said, and nobody has to say "remember this" for it to stick [s1c5].

That matters more because of what is on the other end of the pipe. Cowork is not a text box that answers back. It runs tasks, including in the cloud, and it operates on the user's machine [s1c12]. In July, researchers found Claude Cowork could read credentials on a Mac after escaping its local virtual machine [s1c13]. A system with that reach, now carrying months of accumulated context about the person operating it, is a different object from either half [s1c14].

The surface is also wider than the two products named in the announcement. A recent change put Cowork inside the Claude for Chrome extension, and browser side-panel conversations became part of a user's usage history, according to Igor Bonifacic writing for Engadget [s1c15]. Bonifacic also notes Claude has had memory since last summer, kept fragmented partly by design and partly by architecture [s1c16]. The fragmentation was doing work. It is now gone in two places and still present in a third: Claude Code went unmentioned, and ZDNET's David Gewirtz was told the update is focused on Cowork and chat [s2c1].

The controls are real and worth reading precisely. Retained memory sits as a list of files under Topics, editable and deletable, and a correction propagates [s1c6]. Sensitive categories are off by default, they do not apply retroactively, and Claude shows a notice each time it saves one [s1c8]. Identification numbers, criminal history and immigration status stay out entirely [s1c9]. Gewirtz's objection to the notice is the operational one: a person seeking help with something difficult, warned each time they raise it, may simply stop raising it [s2c2].

Then there is the split that tells you how Anthropic reads its own risk. Consumers get memory on, across Free, Pro and Max, on web, desktop and mobile [s1c2]. Team and Enterprise do not: admins control availability and it stays off for individuals until they switch it on [s1c10]. Gewirtz described the enterprise position slightly differently, as off for organisations by default and subject to eligibility [s1c11]. The two accounts differ, which is itself the finding for anyone writing policy this week. Buyers with a procurement process were given a gate. Everyone else was given a product that already knows things.

The governance consequence follows from the direction of flow rather than from any single toggle. Two-way memory means something disclosed in a personal chat can surface in work Cowork produces, and work context can surface in chat [s2c3]. Anthropic's own illustration is a manager's name and preferred format for updates arriving unprompted in a draft [s1c17]. That is useful. It is also a data path that did not exist on Monday, running between a casual register and an output someone else reads.