Use Cowork in the latest Claude apps and you will notice projects in two places: the chat projects you already know, and a separate Projects menu on the Cowork side. Since they share a name, a natural question follows — do the files and memory you have built up in a chat project carry over to Cowork? This guide answers that with the official support docs and a hands-on test, in plain terms.
🟢 Model references match the current lineup · model notice · Fable subscription
Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (
Update (September 27, 2026): Since September 16, 2026 Cowork is built into every conversation and the Chat/Cowork picker is gone (rolling out to Pro and Max; Anthropic's words: "Claude Cowork is now just Claude"). File and folder work still happens in the desktop app, and scheduled tasks run in the cloud. Any "pick a mode" wording below reflects the pre-integration state. Details: Claude Cowork explained (after the integration).
Two kinds of projects?
Yes. A chat project is a cloud-stored workspace on web and apps that groups conversations by topic; upload files once and every conversation in it can reference them. A Cowork project groups Cowork tasks instead — per the official docs it works similarly, but it lives locally on your desktop. There is no cloud sync for Cowork project data at this time.
In other words, same name, separate spaces. Nothing appears automatically on the other side. So what actually carries over? We tested it.
Our test — files carry over, memory does not
The method was simple: inside a chat project full of documents and accumulated memory, we switched to Cowork mode and asked two questions. One asked for a value written only in the project files (a server region), the other for a value present only in chat memory (the next day's planned tasks).
The results split exactly as shown. The session answered the file-based question correctly, citing the source files, but said the memory-only information was nowhere in the documents. That matches the official docs: what Claude remembers about you in chat does not yet carry into Cowork sessions, and Cowork-side memory accumulates only within Cowork projects.
- Carries over — knowledge files and project instructions. Cowork sessions read and cite them.
- Does not carry over — memory built up in chat conversations (progress, decisions, habits). Cowork sessions do not know it.
Moving a chat project into Cowork — Import
When creating a Cowork project you get three options: start from scratch, Import from a Claude project, or use an existing folder. The second is the key one — search for your chat project, pick a save location, click Create, and its files and instructions transfer into the new Cowork project. If you have a long-running chat project, this is the easiest starting point.
Two caveats: bulk import is not supported (one project at a time), and the docs describe a “transfer,” which suggests a one-time copy at creation — nothing states that later edits to the chat project sync automatically, so re-import if the original changes significantly.
What a Cowork project contains
- Instructions — tone, formatting, and rules applied to every task in the project.
- Scheduled tasks — recurring tasks scoped to the project.
- Context — add a local folder, link a chat project, or paste a URL for reference.
- Memory — Claude remembers context from work within the project and applies it to future tasks there. Memory is scoped per project; what it learns in one does not carry to another.
Current limits worth knowing
- Cowork projects were initially desktop-only with local storage, but with remote sessions (beta) they are expanding across desktop, web, and mobile (rolling out by plan, per Anthropic’s official guidance). Cowork sessions for projects tied to a local folder, and some features such as live artifacts, still work through the desktop app, which must be on the latest version.
- Not available in Claude Code yet (support is planned).
- Project sharing is not supported, even on Team and Enterprise plans.
- Archiving removes a project from the UI only — local files and folders stay untouched.
Practical tips
- If a Cowork task depends on current status, write that background into the prompt — chat memory will not follow you there.
- A Cowork session knows only what the files know. Keep your project documents current; stale docs mean stale work.
- When connecting a folder with important originals as context, start with a copy.