A practical guide · Reviewed October 8, 2026
Keep your Claude context.
Save the research you want to reuse, retrieve it in your next connected task, and keep the supporting passages with the result.
Our real example asks: How do Claude Chat, Cowork and Code carry context? The same saved public research becomes this map and a short guide.
Know what carries forward
Native memory and explicit source retrieval serve different purposes. Chat and cloud Cowork can share memory. Projects keep their own scope. A connected tool can retrieve the specific Multiplist record you ask for.
| Where you work | Native memory | Supporting seed |
|---|---|---|
| Claude Chat | Memory depends on settings and project scope. | [1] |
| Cloud Cowork | Can share native memory with Chat. | [1] |
| Local Cowork | Does not use shared Chat/cloud memory. | [1] |
| Projects | Each has its own memory and summary. | [2] |
| Claude Code | Instructions and machine-local auto memory. | [4] |
Account rollout and settings affect the experience.[3] Code’s instruction files and local auto memory do not establish automatic synchronization with Chat.[4]
Repeat the handoff
- Save the material you want to use. Use the Multiplist extension’s Save to Multiplist Vault action or import your research. Confirm its title and review date in the vault.
- Connect the correct vault. Open Claude’s Multiplist setup, sign in to the account holding the source, and complete authorization. In a new chat, use + → Connectors → Multiplist to enable it. Setup documentation.
- Retrieve before continuing. Ask for the saved research by title, inspect the returned version, and create the next useful result. The prompt below is the one illustrated in our tutorial.
- Inspect the evidence. Open a numbered citation in the original brief, read its complete seed text, and follow its return link. Seeds here quote our public research notes; primary documentation is linked in that brief.
- Keep the answer and evidence together. Preserve the question, review date, supporting passages, and unresolved questions.[7] Attach the file in a supported client or retrieve the source through its connector.[5] An upload does not guarantee persistent memory.[6]
Ask for the saved research
Find our Claude Memory Boundaries research in Multiplist. Create a concise visual guide to carrying context between Claude tools. Cite the supporting passages, identify the source version, and flag anything outdated.
Replace the research title and requested output with your own. If no source is found, check that it was saved, that you authorized the same account, and that the connector is enabled.
Included in this download
This guide, its map, the retrieval prompt, and the unchanged cited brief with eight complete public research seeds. No private legacy transcripts, account details, full upstream documents or production screenshots are included. Reading the files requires no Multiplist account. Creating Archivist briefs is a Multiplist Plus feature.[8]
The map and guide are client-authored analysis. The seeds are evidence from our notes, not verification of a live Claude account. Their stored line coordinates are recorded locators, not verified character spans. Product behavior may change after the review date.
Source version and snapshot checksum
Source: Claude Memory Boundaries — Public Demo Research — October 8, 2026
Source ID: 923aa15c-bb3d-449a-8f3c-9869d53c8a55
Original synthesis generated: 2026-10-08T19:10:00.975Z
Original capsule exported: 2026-10-08T19:10:00.991Z
Payload SHA-256: 281a486ef9a8fd590aec2acbea79d9a8d7db93c2961bf8ca8f0e13384f05f97c
The checksum covers the original exported payload, excluding its integrity field. It checks that snapshot; it does not prove authorship or factual truth. The diagram and this guide are separate derived assets.