# Claude memory boundaries — public demo research notes
Reviewed: 2026-10-08. These are original research notes based on public documentation, prepared for a Multiplist demonstration. They contain no private customer or founder context. They are evidence about documented behavior, not a live test of a Claude account.

## Chat and project memory
Anthropic's memory guide distinguishes project memory from non-project chats. Each project maintains separate memory and a project summary. Chat memory can carry into cloud Cowork tasks, while computer-local Cowork sessions do not use that shared memory. Check the execution environment and memory settings before expecting continuity.
Reference: https://support.claude.com/en/articles/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context

## Project context
A project combines files, instructions, context, and memory. A project tied to an existing local folder remains on that computer. The older Cowork project guide describes memory scoped to the project. The reader should distinguish project context from account-wide continuity.
Reference: https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork

## A changing product experience
Anthropic is gradually merging chat and Cowork into a single conversation experience, initially on Pro and Max. Accounts can be at different rollout stages. The current guide says memory from computer-local Cowork tasks stays with those tasks. A universal claim that chat and Cowork never share memory is outdated.
Reference: https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

## Claude Code is a separate context mechanism
Claude Code carries context through instruction files such as CLAUDE.md and through auto memory. Its auto memory is machine-local and shared across worktrees of the same repository. This does not establish automatic synchronization with Claude chat memory.
Reference: https://code.claude.com/docs/en/memory

## Reusing a file in Claude
Anthropic lists HTML as a supported document upload format. A recipient can attach a brief capsule as reference material. Uploading a file does not promise that every embedded record will enter persistent memory.
Reference: https://support.claude.com/en/articles/8241126-upload-files-to-claude

## Portable context as an explicit handoff
For a portable handoff, preserve the research question, concise answer, evidence, review date, and unresolved questions in a file. A reader should be able to inspect the supporting text before reusing the answer. A dated evidence snapshot remains useful when provider interfaces change. It does not automatically synchronize accounts or certify the truth of source claims.

## Multiplist demonstration boundaries
The shareable demonstration uses public research notes, canonical Neuron extraction, a client-authored synthesis, and the existing v3 HTML capsule renderer. The local video shows the actual exported file. It does not stage a production generation screen or claim a tested upload into a different AI account. Creating Archivist briefs is a Plus feature; reading a shared static HTML file requires no Multiplist subscription. The download carries the brief and complete selected evidence records, not the full upstream documents. Review included text before sharing.