Claude Cowork memory can carry useful context into another session. For a project you need to resume accurately, I would still save a short handoff note with the decisions, finished work and next step.
Remembering that you are building a bakery website is useful. Knowing that the home page is finished, online payments were ruled out and delivery is still undecided is what lets the next session get back to work.
Here is the save-and-resume method I demonstrate with a fictional bakery project. You can start with the free Save where we are prompt, then keep the result in one small file.
What does Claude Cowork memory actually keep?
Claude stores individual memory topics as you chat. You can inspect, edit or delete those topics in Settings under Memory. This is selected context, not a complete transcript of everything you said. Anthropic documents it in its memory guide.
A remembered topic may include a project decision. The limitation is that you have not necessarily checked whether all the details needed for the next task are there, current and correct. A handoff gives you one place to do that review.
Projects also matter. Anthropic says Cowork project memory stays within that project. Context learned in one project does not automatically carry into another. Keep related work together, and check that you opened the right project. See its Cowork projects guide.
If you are new to the tool itself, my plain explanation of Claude Cowork covers the broader idea. This guide is about carrying a particular piece of work into a new session.
Cloud and local sessions have different memory behavior
Anthropic says regular chat memory is shared with Cowork tasks that run in the cloud. Local-only Cowork sessions do not use that shared memory. Having a folder connected is not, by itself, proof that a session has the same memory as your chats.
Checked October 1, 2026. Anthropic has announced that new Pro and Max Cowork tasks will run in the cloud from October 6. Existing local tasks stay local. Its cross-device guide explains the transition.
That guide also distinguishes cloud execution from local file access. Claude can read and write connected folders through the desktop app while it is open, within the permissions you set. Your working folder is real project storage, so check any file changes.
Keep standing instructions separate from project status
Instructions are useful for rules you want applied repeatedly. For the bakery, those might be cream and dark brown colors, friendly English and a requirement to ask before deleting files.
In Claude’s newer experience, Cowork Global instructions have moved into Instructions for Claude under Settings, then General. The rollout is gradual, so your interface may differ. Anthropic’s unified Claude guide explains the change.
Use project or folder instructions for rules specific to that work. Put changing status in the handoff. Otherwise, yesterday’s instruction to build the order page can still be hanging around after that page is finished.
Save your progress in six short sections
At the end of a useful session, open Save where we are, copy the prompt and paste it into that same chat. It is free to copy, with no account or newsletter signup required.
- The goal. What you are trying to finish.
- Decisions and reasons. What you chose and why.
- Current status. What is done and what is still in progress.
- Important facts. Names, numbers and constraints needed next time.
- Open questions. Anything you have not resolved.
- The next three steps. A short, practical starting point.
The prompt asks for fewer than 300 words. It also tells Claude to use only the conversation, avoid adding things you did not discuss and label guesses. Those constraints help keep a plausible suggestion from quietly becoming an agreed decision.
Read the result before saving it. If the chat omitted an important decision, add it yourself and make the correction explicit. A tidy note can still be wrong.
A fictional bakery example shows why the details matter
For the prompt library, I used a made-up chat about Crumb & Co, a bakery whose customers want to request birthday cakes online. Claude Sonnet produced the original example in one run on September 26, 2026. That original answer is shown unedited in the prompt’s full example.
The useful part was how much a new session could recover from a short note. Here is a summary of the fictional project, rather than a verbatim copy of that answer.
- Chosen approach. A request form emails the bakery owner. Online payments are excluded because she is not ready to accept them. Squarespace is the platform because she already has an account.
- Finished work. The home and menu pages are done. The order request and FAQ pages have not been started.
- Useful constraints. About 15 phone orders per week, mostly local parents, and at least five days of lead time.
- Still undecided. Delivery versus pickup only, and whether to add a gallery of past cakes.
Before saving the working handoff, I added an address field in case the owner chooses delivery. That was my later edit, not part of Claude’s original answer. The added field did not resolve the delivery question. Keeping that distinction prevents the next session from assuming delivery is approved.
Start the next session by reading handoff.md
Save the reviewed note as handoff.md in the actual folder you use for the project. The .md extension means Markdown, a plain-text format. You do not need a special memory database to read or edit it.
If Claude has permission to write there, ask it to save the note and show you the exact path. Open the saved file and check it. A reply saying it saved something is not the same as seeing the file where you expect it.
In a new task, select the same project folder and begin with this request.
Read handoff.md in this project folder. Summarize where we left off, the unresolved questions and the next step. Do not change any files yet. If you cannot find the note, tell me rather than guessing.
Check the summary before authorizing work. In the bakery example, I would expect it to preserve the request-form decision and leave delivery undecided. If it proposes a payment checkout or says delivery is confirmed, correct that before it starts.
After the session’s work, update that same handoff with what changed and the next three steps. Keep one current handoff per project. If you keep older notes for history, label them clearly so a new session knows which file is current.
You can add a reminder to your project instructions to read the handoff at the start and update it before stopping. Treat that as a reminder, not a guarantee. You still need to check the saved note.
Keep the handoff small enough to trust
A useful handoff makes the next action easier to judge. Preserve reasons beside decisions, remove stale next steps and leave uncertainty visible. Include only the private details the task actually needs, because the assistant you give the folder to may be able to read them.
This is the idea I am building on with Tandri, a system of files and workflows for keeping project context you control. The public download is being prepared. You can join early access to be first to get Tandri for free.
For today, try the smaller habit on one project. Use Save where we are before you close the chat, review the note and start your next session by reading it.
