A guide · ~8 min read
Why Your AI Keeps Forgetting You — And What You Can Actually Do About It
If you've spent months training an AI assistant on how you think, how you write, what you're working on — and then watched it forget all of it overnight — you're not doing anything wrong. The tools themselves are built that way. Here's why, and what's actually worth doing about it.
The problem most people don't realize they have
Modern AI assistants like ChatGPT, Claude, and Gemini are excellent at understanding what you say inside one conversation. Where they fail is the moment you close that conversation and open a new one. Suddenly the model has no idea who you are, what you were working on yesterday, or that you asked it three weeks ago to stop using bullet points in everything.
This isn't a bug. It's the default. Each new chat is, by design, a blank slate. The features that try to bridge that gap — ChatGPT's Memory, Claude's Projects, custom GPTs, system prompts — are all partial. They save fragments. They cap out. They get cleared when you switch devices, sign in to the wrong account, or when the provider rolls out a model update.
The cost is invisible but real: you spend a few minutes re-onboarding the model every session, you accept worse output because the AI doesn't know your context, and you slowly stop trusting it with anything that requires continuity — long projects, ongoing writing voice, evolving plans.
Why this keeps happening
1. Context windows are finite
Every AI model has a maximum amount of text it can hold in working memory at once, called the context window. Even the biggest models (1M+ tokens on Gemini 2.5 Pro, 200k on Claude, 128k on GPT-4-class) fill up faster than you'd think. Once you exceed it, the oldest parts of the conversation are pushed out — and they don't come back.
2. Persistent memory features are opt-in and capped
ChatGPT's Memory feature stores a few hundred short notes about you. When it fills up, it silently drops or rewrites older entries. Claude's Projects feature only persists context within one project folder. None of these systems let you see the full set of stored memory in one place, edit it, version it, or move it somewhere else.
3. Providers reset things on their schedule, not yours
When a provider updates a model, deprecates an old version, or changes their memory architecture, your stored personalization is one of the first things to drift or vanish. There's no notification when this happens, and no rollback. (For more on this specific problem, see our companion article on model updates and memory loss, our guide to organizing the prompts you actually reuse, or our overview of the major AI personal assistants.)
4. There's no standard format for AI memory
Your ChatGPT memory cannot move to Claude. Your Claude project cannot move to Gemini. There is no MP3-equivalent for personalized AI context — every provider has its own walled garden, and none of them are incentivized to make their format portable.
Five things you can actually do about it
1. Turn on the built-in memory features and audit them weekly
ChatGPT Memory and Claude Projects are imperfect but free. Switch them on, then once a week open the memory panel (Settings → Personalization → Memory in ChatGPT) and delete anything wrong or outdated. Treat them like a sticky-note drawer — useful for a handful of important facts, not a long-term archive. Best for: casual users who only use one tool.
2. Keep a personal context document and paste it into new chats
One page. Plain text. Things any AI should know about you: who you are, how you write, current projects, preferences, things you don't want it to do. Store it in Notes, Obsidian, or a doc. At the start of an important chat, paste it as the first message. It's clunky but free, fully under your control, and works with every model that exists. Best for: people who want zero dependencies and don't mind the friction.
3. Export your chat history on a schedule
ChatGPT: Settings → Data Controls → Export data. Claude: Settings → Account → Request data export. Both deliver a ZIP of your conversations by email within a few minutes to a day. Set a calendar reminder to do it monthly, drop the file in your cloud drive or encrypted backup. This won't make your AI smarter, but it means you never permanently lose a conversation you cared about. Best for: anyone using AI for work with any institutional memory value.
4. Use a local notes app as a manual memory log
After a useful chat, copy the key takeaways into Obsidian, Apple Notes, Notion, or whatever you use. Tag them. Now your memory lives in a tool you control, and you can search it across years even as your AI tools come and go. The downside is it's manual — you have to remember to do it. Best for: people who already live in a notes app and don't want another tool.
5. Use a dedicated persistent-memory layer
A handful of tools now sit between you and the AI providers and hold your context separately. Konshus (us) is built around this — it ingests your existing ChatGPT and Claude exports, distills them into a portable profile, and lets you carry that profile across any model. There are also broader multi-model wrappers (Poe, OpenRouter) that bring memory features of their own. The honest tradeoff: you're trusting one more company with your data, so the bar for encryption, export, and deletion policies should be high. Best for: heavy users, people who work across multiple models, anyone whose AI history has real ongoing value.
How to evaluate any memory or persona tool
If you decide to try a third-party memory layer — ours or anyone else's — here's the short checklist worth running through before you trust it with anything important:
- Can you export everything? In a format you can actually use somewhere else — JSON, Markdown, plain text. Not just a screenshot or PDF.
- Can you hard-delete? Not "deactivate," not "archive" — fully erased on request, with a clear timeline.
- Is your data used for training? Look for an explicit no, in writing, on paid tiers. Anything vague means yes.
- Is it encrypted at rest? Bonus points if individual entries are encrypted, not just the whole database.
- Does it work with more than one model? A memory tool that only feeds one provider has the same lock-in problem you're trying to solve.
- Who's behind it and how do they make money? Free tools that don't sell anything are usually selling you. Tools with a clear paid plan have an honest business model.
If a tool fails two or more of those, don't use it for anything you'd be upset to lose.