By the end of this lesson, you will know where a Project's memory lives and how to keep it current. A Project's custom instructions are its memory. There is no separate memory feature running in the background, so keeping a Project current means editing its instructions when a fact changes.
People expect Claude to "learn" their preferences over time. A Project does not work that way. Anything that should always be true has to live in the custom instructions. Once you know this, you stop repeating the same correction in every chat and make one edit instead.
1How a Project Actually Remembers
A Project's custom instructions are what persist across every conversation inside it. There is no separate memory to manage and no learned-preference feature. If something should always be true, it lives in the custom instructions.
Persists across every chat in the Project:
- Your custom instructions.
- Your uploaded Project knowledge.
Does not persist:
- Anything said in one chat.
- Mid-conversation corrections.
- Preferences you assume Claude picked up.
A Project does not quietly learn your preferences between chats. The custom instructions and uploaded files are the entire memory. If a fact is not written there, the next chat will not know it.
2Update the Instructions When Facts Change
When a standing fact changes, open the Project and edit the custom instructions. Every future chat uses the updated version immediately. This step shows the kinds of facts worth keeping current and how to update them.
- Open your Project and edit the custom instructions.
- Add or change the standing fact.
- Save.
- Start a new chat inside the Project and confirm the updated fact is in effect.
| Role | Standing Fact | Add It When |
|---|---|---|
| HR | "My default output format is a table, one row per item." | You want a consistent format on every answer |
| HR | "My lead hiring manager is now [Name]; address candidate summaries to them." | The lead hiring manager changes |
| Legal | "Our jurisdiction changed to [State]; assume that governing law when none is stated." | The governing jurisdiction changes |
| Marketing | "We added [term] to the banned-words list; never use it in public copy." | The banned-words list is updated |
| Industrial Engineering | "The owner of [work center] is now [Name]; route escalations to them." | A work-center owner changes |
| International Relations | "Our counterpart contact at [ministry] is now [Name/title]; address correspondence to them." | A counterpart contact or protocol rule changes |
If you correct Claude the same way in every chat, that correction belongs in the custom instructions. Put it there once and you stop repeating it.
Verification
If a new chat does not use your updated fact, confirm you saved the change in the custom instructions field. The columns in Step 1 show what persists and what does not.
Related Resources
- claude.ai — The Claude AI platform
- Claude documentation — Official documentation
- Claude support — Help center and troubleshooting
Lesson complete
You now know where a Project's memory lives and how to keep it current with a single edit to the custom instructions. Think of the one thing you correct in every chat, add it to your custom instructions today, and confirm the next chat gets it right on its own.