Key takeaways
- Claude Code's memory is a file, not a setting. A short plain-text file in your project folder that the app reads first, every session, before it does anything else.
- It ends the re-explaining tax. Your voice, brand, and rules live in the file instead of your memory, so you never type them twice.
- It stops output drift. Fix the instruction once and the tenth piece matches the first, because your rules no longer change with your mood.
- You create it by asking, never in a terminal. Tell Claude to save it as the project memory, and it writes and keeps the file for you.
- Keep it short and grow it with corrections. A handful of standing rules, plus every fix you make twice. Not a novel.
- Memory, a second brain, and a skill are different jobs. Memory is how it behaves, a second brain is what it knows, a skill is how it does one task. Set the memory first.
The Solo Creators AI Studio
Get this skill, and every one I build.
The whole vaultA new drop monthlyBuild live with meYours to keep, forever
See inside the Studio
30-day money-back guarantee. Cancel anytime.
Questions people ask
What is Claude Code's memory in simple terms?
It's a short plain-text file that lives in your project folder. Claude Code, the Claude desktop app, reads it at the start of every session before it does anything else. Whatever you put in it (your voice, your brand, your rules, where your files live) becomes the standing truth for that project, so you stop re-explaining yourself in every new chat.
Do I need to code or use a terminal to set up the memory file?
No. You create it the same way you do everything in the app: by asking. Type something like 'save this as your memory for this project and read it every session,' then list your rules in plain English. Claude writes the file and keeps it. You can open the app's built-in file editor any time to read or add a line. No terminal, no commands, no code.
What should I actually put in the memory file?
Keep it short and specific: a line or so on who you are and what you do, your voice rules (the non-negotiables), your brand basics like colors and logo, your do's and don'ts, and where your files live. It's a briefing for a new hire, not your life story. A good memory file takes about 10 minutes to write.
How is memory different from a second brain?
Memory is how the app behaves: a short set of standing rules it follows on every task. A second brain is what it knows: a growing library of your notes and past work it can search when a task needs context. They work together. Set the memory first, because every note and skill after it inherits your voice automatically.
Will one memory file work across all my projects?
Memory is per-project. Each project folder can have its own memory file, so your coaching practice and your side newsletter can behave differently on purpose. If you want the same rules everywhere, you copy the same lines into each project's memory.
How do I keep the memory file from getting stale?
Grow it with your corrections. When Claude gets something wrong and you fix it, add that fix to the memory file. Do that for a week and the same mistakes stop coming back. The file should evolve as your business does, but stay short: standing rules only, never today's task.
Where does the memory file actually live, and is it locked into the app?
It lives as a plain text file in the folder you point the app at for that project, and it is not locked in. Because it is plain text you wrote in plain English, you can open it in any editor, read every line, and move it. There is no database and no proprietary cloud setting. The app just reads that file first at the start of every session.
How long should a memory file be?
Short. A handful of lines covering who you are, your voice, your brand, your do's and don'ts, and where your files live. A memory file crammed with everything becomes noise the app skims, so keep it to the rules you actually repeat and grow it only from real corrections.
Written by Ronnie Nijmeh
Ronnie spent 18 years building a SaaS with a team of 20 that served over 650,000 customers, generated over $14M in sales, and sent over 550M emails. Now he's solo, solving real business bottlenecks and turning them into working AI skills, workflows, and automations. He teaches all of it, with direct access to him, inside the Solo Creators AI Studio Skool community. See what he's built →
“I completely rebuilt my site using the Website Launch Builder. If you've ever built a website, you'll really appreciate this skill. I'm blessed to be a member.”
Michael HattawayFounder, Iron Strengthens Iron