Automation20 September 2026

How to get one Claude project to remember your work, instead of starting from zero every time

A standing Claude project can remember everything from last time, so next time you continue instead of explaining the whole thing again.

Every time you come back to a task that repeats, a client update, a monthly report, a marketing post, you start over. New chat, explain who you are, what you already tried, what last week's version looked like. All of that explaining is time you're not actually saving.

Here's how to set up one Claude project that remembers everything between sessions, a prompt to copy for the setup, and what to check before you rely on it.

Start with the basics

A Claude project isn't just another chat, it's a workspace that stays open. This week Claude announced that projects now run from a single conversation: you describe what needs doing, and Claude manages several threads in the background, continuing to work even after you close your laptop. You still talk to it in one place, it's the one splitting up the work.

Step 1: pick a task that repeats, not a one-off

Not "write me one email", but something you do every week or month: a client status update, a sales report, a draft post. That's what gives the project something to remember.

Step 2: set up the project once, with the full context

Use the prompt below when you start it. It tells Claude explicitly to treat this as a standing place, not another chat.

Prompt to copyFrom today, this is our standing project for [name the task, e.g. weekly client update]. Remember everything that happens here between sessions. Every time I come back, continue from where we left off last time, don't start from zero and don't ask me to re-explain the background. If there are a few things to work on at once, split them into separate threads inside this project and update me when something's ready.

This wording matters because it tells Claude not to reset itself every time you open it, which is exactly what turns a project into something different from a regular chat.

Step 3: go back to the same project, even when a new chat feels faster

The temptation is to open a new chat "just this once" because it feels quicker. That's exactly what breaks the memory. If the task belongs to the project, open the project.

Wait, before you rely on it

A project that remembers everything is also a place where mistakes can quietly pile up if nobody checks. Every so often, ask it directly "what do you know about this project so far", to catch anything that drifted. And don't put anything in a standing project you wouldn't want permanently accessible in one place, like passwords or full financial details.

What happened to someone who did this

Claude Code creator Boris Cherny wrote that moving to one project changed not just how he talks to Claude but how he codes at all: "I stopped managing sessions. I just send thoughts as they come, Claude splits them into threads, and the project remembers how I work." On the other side, Codex's Nick Baumann describes a three week old thread that checks his Slack, Gmail and PRs every hour, turning noise into something he can act on. He put it simply: "I have become monothread pilled."

Do this next

Think of one task you've done more than twice this month. Next time it comes up, don't open a new chat, set up one project for it with the prompt above, and come back to that same project next time instead of starting over.