Onbrandechocom logo for branding and marketing.

Why Claude forgets everything you told it yesterday

An open notebook with writing on the left page fading out toward a blank right page

You explained something important to Claude last week. A client detail, a brand rule, a preference you’d rather not repeat. Today, in a new chat, Claude has no idea it ever happened.

This isn’t a fault. It’s how chats work, and once you understand it, a lot of your frustration with Claude disappears.

Chats don’t talk to each other

Each chat is its own separate conversation. Nothing you say in one carries over into the next, unless that information lives somewhere Claude reads automatically.

That “somewhere” is a Project. A Project has three parts: custom instructions, knowledge files, and the chats themselves. Claude reads the instructions and the files in every single chat inside that Project. The chats don’t share memory with each other directly, but they all draw from the same instructions and files sitting underneath them.

So the memory isn’t really memory at all. It’s a shared reference library that every chat happens to read before it answers you.

Why this matters more than it sounds

Most people treat Claude like it should remember things the way a person does, through conversation alone. When it doesn’t, they assume they’re doing something wrong, or that Claude just isn’t that smart.

The real issue is that anything important was never written down anywhere permanent. It lived in a chat that’s now closed, and closed chats don’t feed anything.

Once you see this, the fix is obvious: anything you don’t want to repeat has to go into a file or an instruction, not just into a conversation.

One thing to do today

Open a Project. Give it a specific name, not a vague one. “Client emails” tells Claude and future-you a lot more than “Work stuff.” A specific name forces you to think about what actually belongs in there, which keeps the Project focused instead of becoming a dumping ground.

Then add one piece of information you’re tired of repeating; a tone preference, a fact about your business, a formatting rule, into either a custom instruction or a short knowledge file. That’s it. You’ve just given every future chat inside that Project something it would otherwise have to be told from scratch.

The temptation to over-fill it

It’s tempting to dump everything you know into a Project on day one. Resist that. A thin, tidy bank that Claude can actually use well beats a bloated one stuffed with files nobody re-reads. Start small, and let the Project grow as you find out what you keep needing to repeat.

That’s the real shift here. You’re not trying to make Claude remember you. You’re building the one place it reads from every time, so you never have to explain yourself twice.

Claude KnowledgePrint builds on this first container, covering how to turn it into a proper knowledge bank, including story files, objection libraries, and systems for running content in batches. Find out more about Claude KnowledgePrint.

Colin James, founder of OnBrandEcho

Colin James

20+ years building things on the internet, now focused on getting on-brand results from Claude. More about me →

Malcare WordPress Security