Melbourne, Australia
Read · Test · Keep
Set up a control project so a new session knows where every job is up to
A made-up candle shop shows the folder, the two kinds of file and the question a new Claude Code session answered, then you set up your own.
Say you opened a brand new AI chat and typed this. What would come back?
What am I working on and where is each job up to?
If you brief your AI again at the start of every chat, you know the answer. An earlier Growth File, Why AI gives poor results when it is not set up properly, shows what to give the tool.
Here is that question asked twice, each time in a brand new Claude Code session, with nothing else typed.
Before. In an empty folder with nothing set up, and no way to look anywhere else on the computer, the answer began:
I don't have a record of your jobs in this conversation, so I can't tell you what you're working on or how far along each piece is.
After. In a folder set up the way this guide shows:
You have two jobs in projects/, both for Harbour Lane Candles:
1. Product photos (winter range)
- Done: The shot list is written. Six of the ten candles are photographed.
- Next: Photograph the last four candles.
2. Spring sale email (to your customer list)
- Done: The subject line is written.
- Next: Draft the body.
I only read the status files, so I haven't changed anything.
The second Claude Code session knew because of two kinds of file in its folder: one instruction file, CLAUDE.md, and one status note, STATUS.md, for each job. A folder set up this way is what this guide calls a control project: a brand new session reads those files and can tell you what you are working on and where each job is up to. The business in the answer, Harbour Lane Candles, is made up for the example.
For this guide the setup was built twice from scratch, each time in a clean folder. Both times the new session got the question right. This guide takes you through the same setup. Its last step is you asking the question yourself.
Why I work this way
I'm a developer and a marketer, and I run my work through Claude Code. This is how I already work. Before it, I would be starting projects from scratch. The AI had no memory, so every new project meant it was effectively learning everything again.
Now I have one working project. Any new project gets filed in a specific folder, so I can ask that one project about any of them and it knows what it is and where it is. From 19 October to 18 November 2026, about 97% of my Claude Code sessions ran in that one project.
I ask the question at the top myself. In the same month, 20 of the 103 sessions I started opened by asking to pull a job back up or asking where it had got to.
You do not need to be a developer to follow this. You type three short commands to start, and two more to open a new session for the test. Everything else is a request in plain words.
What you get, and what is not promised
You get one thing you can check: a new session that tells you your jobs and where each one stands.
There is no claim here about time saved. That was not measured.
The trial ran on a Mac, in a terminal window. Windows was not trialled. Nor was doing this in ChatGPT, or in Claude chat without Claude Code.
You need Claude Code installed and signed in before you start. This guide does not cover installing it.
In the trial the setup request took about 20 seconds to run. Typing your own version of it is the slow part.
There are two ways through. Read "Watch it once" to see the whole thing done with an example. Or go straight to "Your turn" and look back when you get stuck.
The three parts of a control project
This is the whole setup. Each step in from the left is one folder deeper.
ai-home/
CLAUDE.md
projects/
spring-sale-email/
STATUS.md
product-photos/
STATUS.md
- The home folder. One folder for everything, at the top of the picture. The trial called it
ai-home. - The instruction file. A file named
CLAUDE.mdin the home folder. It says who you are, how you write, and where your jobs live. - The status note. Every job gets its own folder inside
projects/. In it sits aSTATUS.mdthat says what the job is, what is done, and the next step.
The picture shows two jobs, so it shows two status notes. A status note is like the note you would leave on the bench for someone covering your shop tomorrow.
Watch it once
The business below is Harbour Lane Candles, the made-up one from the top of the page.
1. One folder. A folder named ai-home was made, and Claude Code was started in it.
2. One request. This was typed in plain words:
Set this folder up as my control project. 1. Write a file called CLAUDE.md here. In it say: I run Harbour Lane Candles, a one-person candle shop. I write in plain, friendly Australian English. Every job I am working on has its own folder inside projects/, and each job folder has a STATUS.md that says what the job is, what is done, and the next step. When I ask what I am working on, read every STATUS.md in projects/ and tell me. When a job moves forward, update its STATUS.md before you finish. 2. Make the projects folder. 3. Make my first job folder, projects/spring-sale-email, with a STATUS.md that says: the job is the spring sale email to my customer list; the subject line is written; the next step is to draft the body. Then tell me what you made.
Look at item 1 again. Its first two sentences are the briefing you keep retyping. The third says where jobs live. The last two are rules: read every status note when asked, and update a note when a job moves forward.
Claude Code made three things, then listed them:
CLAUDE.md, holding those instructions- the
projects/folder projects/spring-sale-email/STATUS.md, which read:
# Spring sale email
## What the job is
The spring sale email to my customer list.
## What is done
- The subject line is written.
## Next step
Draft the body.
3. A second job. This was typed next:
Add a new job called product-photos. The job is new photos of the winter range for the shop page. The shot list is written and six of the ten candles are photographed. The next step is to photograph the last four candles.
Claude Code made projects/product-photos/STATUS.md, with the same three parts.
4. The question. A brand new session was started in the same folder and asked the question from the top of this page. Nothing else was typed. It gave the answer under "After" at the top of this page.
It knew because it read the instruction file and the status notes.
Your turn
Use your own business and a job you are really working on.
1. Make the home folder and start Claude Code in it. Open the Terminal app. Type these three lines, pressing Enter after each:
mkdir ai-home
cd ai-home
claude
The first makes the folder. The second steps into it. The third starts Claude Code there. Pick your own folder name if you like, and use it in both lines.
Because the folder is new, Claude Code asks: "Is this a project you created or one you trust?" In the trial the highlight sat on "No, exit". Press the down arrow to move it to "Yes, I trust this folder", then press Enter. It asked this once. The next session in the same folder did not ask.
2. Send the request. Type the request from "Watch it once" with four things changed:
- the sentence about your business
- the sentence about how you write
- the name of your first job folder
- what that job is, what is done, and the next step
Leave the two rules as they are. The test at the end leans on the first one.
Claude Code may stop before each file and ask, for example, "Do you want to create CLAUDE.md?" It shows you the file's words first. Read them, then choose "Yes". In the trial it asked twice, once for each file. If it does not ask, it is set to make changes without asking, and it goes straight to the list.
You should see a list of what it made: CLAUDE.md, projects/, and your job folder with its STATUS.md. Your files will not match the example word for word. The two trials gave different wording, with the same three parts in the status note both times. In one trial it added a line that was not asked for, and said so in its list.
Open the status note. If its three parts are true, go on. If not, tell Claude Code what to correct.
3. Add a second job. In the same session, ask for it in plain words, the way the product photos job was added in "Watch it once". Say what the job is, what is done, and the next step.
You should see one more status note, in a new folder inside projects/.
A job folder is not finished until it has its note. In the month I counted, 19 October to 18 November 2026, 44 of my 77 project folders had no status note. I count that as a fault in my own setup.
Test it: ask a brand new session what you are working on
No prompts for this part.
Type /exit and press Enter. That ends the session. Then type claude and press Enter to start a brand new one in the same folder. Ask the question from the top of this page. Type nothing else.
It passes if the answer names every job you set up and, for each one, what is done and the next step. Hold it against your status notes, line by line.
If it does not pass, check these two things. Both were tried.
- A job is missing its details. Look for a job folder with no
STATUS.md. In the trial, a folder with no note was reported like this: "There's no STATUS.md, so I can't tell what this job is or how far along it is." Tell Claude Code the three parts and ask it to write the note. - None of your jobs come back. Check which folder the session started in. In the trial, a session started in a different folder did not find the jobs. Type
/exit, step into your home folder withcd, and start again.
Keep the status notes true
The answer is only as good as the notes. The second rule in your instruction file is there for that, and it was tried once.
In the trial, a session was told: "I photographed the last four candles this morning." Nothing else. It offered a change to the product photos note, from six of ten candles to all ten. The next new session reported the job that way.
One thing to watch. Nobody had said what came next, so it wrote a next step of its own and said it had. When a job moves forward, say the next step yourself.
How the setup holds up after weeks of use was not trialled.
Questions and answers
Do I need to be a developer to set this up?
No. You type three short commands to start and two more to open a new session, and the setup itself is a request in plain words. You need Claude Code installed and signed in first. This guide does not cover installing it.
Does this work in ChatGPT, Claude chat or on Windows?
This guide cannot say, because none of them was trialled. The trial ran Claude Code on a Mac, in a terminal window. The Claude desktop app was not tried either.
Does Claude Code keep the status notes up to date?
The second rule in your instruction file asks it to, and that was tried once. Told only that a job had moved forward, it offered a change to that job's note. It also wrote a next step of its own, because nobody had said one. Say the next step yourself.
One thing to do now
Pick the next job on your list, the one you would otherwise explain to a fresh chat from scratch. Ask Claude Code to add it, with the three parts. Do it now, without this page open.