Claude Code forgot who you are again today

Everyone is arguing about which memory repo wins. Mem0. Claude Cidian. Memory Palace. Most people pick one, install it, and move on.

That is the problem.

Off the shelf memory systems are built for the masses. They do not know your business workflows, your recurring projects, or what you need Claude to retain across sessions. A lawyer needs case precedent recall. An ecommerce operator needs seasonal ad performance and consumer demand patterns. Same tool, completely different memory profile.

I reverse engineered three open source memory repos and built my own stack. Here is the process.

Step one is clone. Pull Mem0, Claude Cidian, and Memory Palace into a local folder.

Step two is audit. Ask Claude Code to spin up sub agents that do a full deep dive on every repo and compare them against each other. Each agent takes about 5 to 10 minutes and runs in the background. The results land in your context window without flooding it.

Step three is extract. Tell Claude what your day to day actually looks like, then ask it to pull only the design patterns and code that fit YOUR use case. Skip everything else.

From there you layer your system on top of Claude's native memory instead of replacing it.

Identity: name, role, anything that never changes. Lives at the top.

Critical context: your business, your current projects, your market position. Sits right below identity.

Working memory: the messy temporary thoughts for whatever you are building right now. Disposable once the task ships.

Long term knowledge: outcomes worth revisiting even if they are not foundational to who you are. A litigation result, a product launch postmortem, a pricing change log.

Episodic memory: why you saved something in the first place. The context behind the entry, not just the entry itself.

Decay and promotions run in the background. Old irrelevant memories lose weight. Frequently called memories rise in importance. The stack cleans itself as your priorities shift.

You do not need a nuclear bomb for a fist fight, right?

Same logic applies here. You do not need a vector database if markdown files already do the job. You do not need semantic search if keyword matching gets you there. Build light. You can always add complexity later.

The technical wiring is straightforward: hooks at session start to auto inject memory files, CLAUDE.md for the broad instructions, and compaction survival to keep long sessions from losing the thread.

The goal is a memory system light enough to maintain and specific enough to actually help. Build yours.

9 comments