Why Claude keeps forgetting you (and how to fix it)
The amnesia is the default, not a bug you caused
After this, you'll be able to name exactly why Claude forgets you between conversations and describe the two systems that fix it, so you stop re-pasting the same context into every new chat.
Before you start
Complete Conversation history: what Claude remembers (and what it forgets) first; this lesson builds on the session-versus-permanent-memory distinction you learned there and turns it into a fix.
The idea
Every Claude conversation starts from zero. You explain your job, your tone, your client, your goal, and get great answers. The next day you open a fresh chat and Claude has no idea who you are.
That is not a fault you caused. Every new conversation is a blank slate by design, because the detail of one chat does not flow into the next one on its own. Two features fix this: Projects (a workspace that holds your standing context) and Memory (a summary Claude builds from your past chats).
Here is the before and after: Before, a copywriter retypes the same 120-word brand brief at the top of every chat, five days a week, twenty-five times a month. After, she saves it once as Project Instructions and just types "draft a re-engagement email," and Claude already knows the brand and the tone.
Now try it: open the chat you used most this week and count how many top lines are background you have typed before. Three or more lines means you have found your repetition.
Re-explaining yourself to Claude is a setup problem, not a prompting problem.
Try it (8 min)
Watch out for
- Assuming Claude forgot you because you did something wrong; the blank slate is the default behavior, not your mistake
- Trying to fix amnesia by writing a longer message each time; longer prompts do not persist into the next chat
- Confusing 'Claude remembered something within this chat' with 'Claude will remember it tomorrow'; only the first is true by default
- Deciding Projects and Memory are the same thing; they are two separate systems and this module keeps them apart
- Putting task-specific details (today's deadline, this one client) into the 'always remember' pile; those belong in the individual message
Paste this into Claude
I use you regularly for the same kind of work, and I keep re-explaining my context in every new conversation. Help me see the pattern clearly. Here is the background I usually paste at the start: [paste the paragraph of context you typically retype, or describe it: who you are, your tone, your audience, any rules you always give] Please do three things: 1. List the pieces of this that almost never change (these are good candidates for permanent Project Instructions) 2. List the pieces that change per task (these stay in the individual message) 3. Estimate how many times per month I am retyping the unchanging parts, and tell me in one sentence why moving them out of every message would help
What good looks like
- Claude separated your context into 'never changes' versus 'changes per task'
- The 'never changes' list contains at least 2 items you genuinely repeat often
- Claude gave you a rough count of how many times a month you retype that context
- You can now point to one specific paragraph you will move into a Project later
When this breaks
- Breaks when you treat every new conversation as a continuation of yesterday's, because Claude has no link between separate chats and will answer with none of your prior context.
- Breaks when you keep solving repetition by pasting more text, because the paste lives only in that one message and disappears the moment you start the next chat.
AI can help with this
Open Claude and paste this: 'I keep re-explaining the same background in every new chat with you. Here is what I usually say: [paste it]. Tell me which parts never change and which parts change per task, so I know what to set up permanently later.'
You can now
You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.
- You can verify that claude separated your context into 'never changes' versus 'changes per task'.
- You can verify that the 'never changes' list contains at least 2 items you genuinely repeat often.
- You can verify that claude gave you a rough count of how many times a month you retype that context.
- You can now point to one specific paragraph you will move into a Project later.
Key takeaways
Claude forgets you between conversations by design. Repeating yourself is a symptom; the cure is moving your standing context into a Project while Memory keeps a running summary of what is true of you across chats.
- Treat the blank-slate start of every conversation as expected behavior, not a fault you caused.
- Stop fixing amnesia with longer messages; text in one chat never carries into the next.
- Separate context that never changes (Project material) from details that change per task (message material).
- Remember that Projects hold standing context you set, while Memory is a summary Claude builds from your chats; they are two distinct systems.
- Spot the repetition signal early; if you retype the same brief weekly, you have a setup problem, not a prompting problem.
Go deeper