Check every way you use Claude. The map of what Claude remembers assembles as you go — what gets in, where it lives, and how it comes back out.
A Cowork session runs remote or local for its whole life — you choose at start (the “Beta” button, or Settings → Cowork → “Run new tasks in the cloud”). Chat and Cowork share one home now, with one place for your projects and artifacts across both; a project tied to a local folder is Cowork-only, desktop-only. A remote session keeps working with your laptop closed, but can reach your local folders and tools only while the desktop app is open and connected — and remote scheduled tasks, which run with no device online, can’t use local folders or local connectors at all. The desktop app remains the full Cowork experience — there Claude can also use your local files and browser. Remote sessions are rolling out over the next several weeks, Max plan first. Not on the map: Dispatch (the persistent assign-from-anywhere thread) and its memory; Claude Code’s nested per-directory CLAUDE.md files, .claude/rules, and subagent memory; managed-policy files; organization instructions (Team/Enterprise — they apply across Chat, Cowork, and Code and outrank yours).
Settings → Profile also holds your name, what Claude should call you, and what best describes your work — lightweight context Claude sees account-wide. The colored tick on each row marks the memory home it touches: Mac, Windows, WSL, cloud, your account, Cowork.