In this analysis
Shared preferences can cross from chat to Cowork without replacing the current task's sources and approved artifacts.
Conversation context crossed a work surface
Claude’s September 11, 2025 memory introduction preceded the January 12, 2026 Cowork preview in the release notes. The August 25 shared-memory announcement connected chat memory with cloud Cowork. The significant workflow change is reduced re-explanation across surfaces. A preference expressed conversationally can inform later work. That continuity should still be distinguished from carrying a verified document, current dataset or completed task artifact into the execution environment.
Remembered intent does not supply missing evidence
An illustrative user discusses a presentation structure in chat and later asks Cowork to prepare the deck. Recalling the preferred structure can improve the first draft. It cannot establish that the numbers from an earlier conversation remain current or that the latest source file is available. A useful handoff therefore separates preferences from task inputs. Otherwise, familiarity can create the impression of a complete brief while the essential evidence has never been attached to the actual assignment.
The artifact carries a different kind of continuity
A saved outline, source table or draft contains details that may not be represented in a general memory topic. Its exact contents matter when a task requires faithful continuation. A shared preference about concise slides is not equivalent to the particular ordering and qualifications in an approved outline. This distinction does not diminish the memory feature. It explains why a workflow may need both persistent personalization and explicit artifacts, each supporting a different aspect of continuity between thinking about work and performing it.
A cross-surface fixture
A practical illustrative test establishes a writing preference in chat, then provides a new source packet for a Cowork task. The review checks whether the output follows the preference while grounding its factual claims in the new packet. A conflicting older example can expose whether remembered context has displaced current evidence. No measured product result is asserted. The fixture tests the intended benefit without requiring every past conversational detail to become an authoritative input, and it keeps the source of a factual assertion recoverable.
Less briefing does not mean no briefing
The August change can remove repetitive explanation about how a person works. It does not remove the need to specify what this particular task is allowed to use and what counts as complete. The useful retrospective lesson is to divide a handoff into remembered working preferences, current evidence and the requested deliverable. Shared memory supports the first category; the others still deserve explicit representation. That division turns cross-surface familiarity into a practical aid while preventing it from concealing a missing input or an outdated assumption.