"Every morning I explain who I am. Every morning it has no idea. Like a very expensive goldfish."— Office Man
Why does it forget?
AI language models work within a context window — everything they can process in a single conversation. When that conversation ends, the window closes. Nothing carries over. The next session starts completely fresh. This is not a design oversight. It is deliberate. Persistent memory requires persistent storage, which raises privacy questions about what is retained and who has access to it. It also introduces the risk of stale context: if the model remembers something that was true six months ago and no longer is, it can confidently use that wrong information. The default of no memory is the privacy-preserving, low-risk default.
What is changing
Some tools are adding memory features. ChatGPT Memory retains facts about you across sessions — you can view, edit, and delete what it stores. Claude Projects maintain a persistent context — documents, instructions, background — across all conversations in a project. Microsoft 365 Copilot draws automatically from your calendar, emails, and documents. Custom Instructions in various tools let you set persistent preferences applied to every conversation. These features are improving but not yet universal, and in many workplace deployments they may be disabled for data governance reasons.
The context file
The most reliable workaround for any tool without persistent memory is a context file: a 150 to 250 word document describing who you are, your role, your sector, your typical audience, your preferences (tone, format, technical level), and any standing instructions. Paste it at the start of any new session. It takes ten seconds and immediately improves the quality and relevance of responses. Most people who try this once find they never go back to starting sessions without it. It is not elegant. It works.
What to do
Check whether your AI tool has a memory or projects feature and spend ten minutes setting it up. Write a context file — role, sector, audience, preferences, standing instructions — and use it for any tool without native memory. Ask your IT team whether persistent context features are enabled or available in your organisation's deployment. Keep the context file current: update it when your role or priorities change. Stale context, confidently applied, can be worse than no context at all.