Claude Code memory: CLAUDE.md, and a memory that follows you to every app
Claude Code is at its best when it knows your project: the architecture, the decisions, the commands that work, and what you did yesterday. Out of the box it knows the code. The rest it has to be told. How Clau
Claude Code is at its best when it knows your project: the architecture, the decisions, the commands that work, and what you did yesterday. Out of the box it knows the code. The rest it has to be told.
How Claude Code remembers today
CLAUDE.md files. Claude Code reads CLAUDE.md at the start of a session: one in your home folder for your personal rules, one in the project for team rules, and more in subfolders when it works there. It is the right place for stable instructions: "use pnpm", "run the tests before you commit", "never touch the migrations folder".
The session itself. Within one conversation Claude Code keeps context, and it can compact a long session so it keeps going.
Where it stops
- Decisions and their reasons. CLAUDE.md holds rules you wrote. It does not collect "we chose Redis over Postgres for the queue because of X" as you go.
- What happened yesterday. A new session does not know which task you stopped at, which approach failed, or what you promised to do next.
- Old versus new. When a plan changes, an old note can sit in a file next to the new one, and the agent cannot tell which is current.
- Your other AI apps. What you decided in Claude on your phone or in ChatGPT at lunch is not in your repo.
Add a memory that writes itself
NestDaddy Memory is a remote MCP server. Connected to Claude Code, it gives the agent tools to save, search and update a long-term memory, plus a record of past conversations:
- "continue what we stopped yesterday" finds the exact place you stopped,
- "the thing we set up three days ago" works, because it searches by time and meaning,
- the latest decision wins: change your mind and the old plan is replaced, with the full history kept,
- any language, so a mixed-language team or a bilingual you still finds everything,
- the same memory is in Claude, ChatGPT, Cursor and any MCP app, on every device.
Connect it
Start your free month at nestdaddy.com/memory (no card), then in your terminal:
claude mcp add --transport http nestdaddy-memory https://nestdaddy.com/memory/mcp
Open Claude Code, type /mcp, choose nestdaddy-memory and pick Authenticate. Your browser opens. Sign in, click Allow, and go back to the terminal.
Tell Claude Code to use it
Add this to your personal ~/.claude/CLAUDE.md, so every project uses it:
# Memory
My long-term memory is the nestdaddy-memory MCP server.
- On every message, first call `recall` with what I said.
- Before deciding anything about a project, search it (`search_memories`, then `get_memory`).
- When we decide something, save it with `save_memory` (one topic per memory; update instead of duplicating).
- After each answer, log the turn with `log_turn`.
- When I refer to earlier work vaguely, use `search_conversations` and `read_conversation`.
Now CLAUDE.md does what it is good at (rules), and NestDaddy Memory does the rest (everything you learn and decide, across every session and every app).
Try it
Tell Claude Code: "Remember that the payment webhook is the next task, and that we chose Stripe Checkout." Close the session. Tomorrow, open a new one anywhere and type: "continue yesterday's work."
Start today
Memory compounds. Every session you run from today makes tomorrow's session smarter. Start your AI's memory today: nestdaddy.com/memory.
Originally published on the NestDaddy blog. NestDaddy gives your AI today's internet: live web search and real-time breaking news from its own index. nestdaddy.com/mcp
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.