In this analysis
Selective retention means a previously mentioned constraint may need to be supplied again in the current task.
Selective memory became an input condition
Claude’s September 11, 2025 memory introduction and the January 12, 2026 Cowork preview preceded the August 25 shared-memory announcement. The update described sensitive-topic controls with selective retention. That makes memory availability part of the task’s input conditions. A continuation cannot assume that every previously mentioned fact has been retained. Absence from persistent context can reflect a deliberate setting rather than a reasoning failure, and the application should not fill the gap by pretending to remember.
Mentioned once is not available forever
An illustrative user previously discussed an accommodation relevant to planning an event. A later planning task may not include that fact in its available memory. Treating prior mention as proof of current availability creates a misleading expectation. The useful response is to distinguish known constraints from missing ones and ask for what is necessary through the ordinary task conversation. This does not require retaining more sensitive information by default. It recognizes that a workflow must remain correct even when a potentially helpful detail has not been preserved.
Enabling a setting is not a historical reconstruction
A user changing retention preferences modifies how future context can be handled under the documented rules. It should not be interpreted as proof that omitted historical details have become available retroactively. The design consequence is a temporal boundary: when a required fact is absent, the task still needs an explicit input. This prevents a setting change from being mistaken for successful data recovery. The point concerns evidence availability, not advice to enable a particular memory category or a guarantee that every possible topic can be stored.
A missing-constraint fixture
A practical illustrative test asks for an event plan with some required constraints explicitly supplied and another intentionally absent. The expected outcome identifies the missing condition before making a dependent recommendation. A second version provides that condition in the current task and checks whether the plan changes appropriately. No private information or real user record is needed. The fixture assesses graceful handling of absent context, avoiding an acceptance rule that rewards the model for inventing a remembered fact or for treating all missing information as irrelevant.
Defaults define limits of continuity
The August change makes memory more useful across work surfaces while retaining user choices about what persists. Those choices mean that continuity is selective, not an assurance of exhaustive recall. The retrospective lesson is to represent available context honestly and preserve a route for supplying missing task constraints. An agent can be helpful without claiming complete familiarity. Correctly noticing that a necessary input is absent can be a successful part of the workflow, especially when the alternative is a confident plan built on an unsupported assumption.