ChatGPT is the most-used AI tool in the world, and it forgets you the moment you close the tab. Or it half-remembers. Or it remembers the wrong thing. Anyone who has tried to use it as a thinking partner for more than a week has hit the same wall: the model is brilliant in the chat, and amnesiac everywhere else.
In April 2024, OpenAI shipped a Memory feature. In 2025, they extended it with chat history references. In late 2025, they added Apps and full MCP support behind Developer Mode. Five distinct ways to make ChatGPT remember now exist, and almost nobody uses more than one of them.
This post is the honest tour. What each method actually stores, where it falls down, and which one to use depending on whether you are trying to remember your dietary preferences, a 50-page contract, or every tweet you have ever bookmarked.
- Saved Memories store short facts (“I am vegetarian”). Free and paid plans. Not for documents.
- Chat history reference lets ChatGPT search across past conversations. Plus and Pro only.
- Custom GPTs hold up to 20 knowledge files for fixed reference material. Frozen at upload.
- Apps (formerly Connectors) let ChatGPT query Google Drive, Notion, Dropbox, and others live. Paid plans, not in EEA or UK.
- Custom MCP servers via Developer Mode give ChatGPT access to any live data source you control, including your own bookmarks.
What “remember” actually means in ChatGPT
Before picking a method, it helps to be precise about what people mean when they ask ChatGPT to remember something.
There are three different things people lump together. The first is personal facts: “I am a senior PM at a fintech, I prefer concise replies, I have two kids.” The second is reference material: a contract, a research paper, a style guide, a folder of notes you want ChatGPT to use as a knowledge base. The third is live data: your calendar, your saved tweets, your team’s Linear tickets, your bookmarks. Stuff that changes.
ChatGPT has a different feature for each one. Stacking them is the secret. Most people pick one feature, hit its ceiling, decide ChatGPT has a bad memory, and move on. The model is fine. The wiring is the problem.
Method 1: Saved Memories (the built-in feature)
Saved Memories is the original Memory feature OpenAI launched in February 2024. Available on free and paid plans. Lives at Settings → Personalization → Memory.
How it works: you tell ChatGPT to remember something (“Remember that I run a SaaS company called Acme”), or ChatGPT decides on its own that a detail in the conversation is worth keeping. The note gets stored as a short text fact. Every future chat starts with all your saved memories in context.
The mechanics are simple and the value is real for the right use case. A vegetarian who says “remember I am vegetarian” never gets recipe suggestions with chicken again. A developer who pins their preferred stack stops re-explaining it every Monday.
The limits matter, though. Each memory is a short fact, not a document. You cannot paste a 50-page PDF and retrieve it later. OpenAI’s memory FAQ notes the system is designed for “context across conversations,” not knowledge storage. Heavy users hit a soft ceiling within a few months and ChatGPT starts asking which memories to delete to make room.
Best for: personal facts about yourself, your work style, ongoing preferences, recurring projects. Bad for: documents, large reference material, anything that changes weekly.
Method 2: Reference chat history (the silent upgrade)
OpenAI quietly rolled out a second memory layer in 2025: the ability to reference past chats directly. This is not the same feature as Saved Memories, though most users do not realize there are two.
Reference chat history works in the background. With it on, ChatGPT can search across every conversation you have ever had with it, pull relevant context from old chats, and use that to inform a new response. Available to Plus and Pro on the web. Free users get a “lightweight” version that gives short-term continuity within a session window.
The big advantage: it is automatic. You do not pin anything. ChatGPT decides what is relevant. The big disadvantage is the same thing. The retrieval is opaque, the results are inconsistent, and you cannot point at a specific old chat and say “use that one.”
Turn it on under Settings → Personalization. Combine with Saved Memories and you have ChatGPT’s full native memory stack: fixed facts plus fuzzy history. For most consumer use, this is the ceiling of what works without doing extra setup.
Method 3: Custom GPTs with knowledge files
If you want ChatGPT to behave like an expert on a body of material, the right tool is a Custom GPT. Available on paid plans only.
A Custom GPT is a saved configuration: a system prompt, a set of tools, and up to 20 attached knowledge files. Any chat started inside that GPT begins with access to those files. ChatGPT uses retrieval to pull the relevant sections into the model’s context as you talk.
This is the underrated method. People who write contracts, run research, or maintain a style guide should be using Custom GPTs and are usually relying on Saved Memories instead. Twenty files at up to 30MB each is a serious knowledge base for one specific job.
The trade-off is that it is frozen reference material. The files do not auto-refresh. If your style guide changes, you re-upload. If you are pointing it at a Notion workspace that updates daily, this is the wrong tool. Custom GPTs are also Claude-style Projects: the same shape, scoped to a single AI client. We compared the two patterns in detail in Claude Projects vs MCP.
Best for: finished reference documents, contracts, style guides, research corpora, a fixed set of articles. Bad for: anything that changes, anything personal, anything you cannot fit into 20 files.
Method 4: Apps (formerly Connectors)
In December 2025, OpenAI renamed the Connectors feature to Apps, with the goal of presenting a unified interface for everything ChatGPT can talk to outside its own runtime. Both interactive UI apps and read-only data connectors live in the same panel now.
Apps cover the obvious enterprise stack: Google Drive, SharePoint, Dropbox, Box, Gmail, Outlook, Google Calendar, Notion, Linear, GitHub, HubSpot, Teams. ChatGPT can search these systems mid-conversation. Ask “what did we agree in the contract with Acme” and Deep Research will scan your Drive and Notion for the answer.
The features are real and they are live. The limits are also real.
First, paid plans only. Free ChatGPT cannot use Apps. Second, not available in the EEA or UK as of May 2026, per OpenAI’s official documentation. Third, Apps is a fixed list. You cannot add an arbitrary third-party data source through this panel. If your notes are in Bear, your bookmarks are in Raindrop, or your saved tweets are in your X account, none of those are Apps.
The combination of “paid, regional, and curated” makes Apps the right answer for a specific user: paid US-based ChatGPT user whose work data already lives in a supported tool. For everyone else, the next method is the one that matters.
Method 5: Custom MCP servers via Developer Mode
In late 2025, OpenAI shipped Developer Mode: a beta toggle that gives ChatGPT full Model Context Protocol support. With it on, you can add any compatible MCP server, not just the ones on OpenAI’s curated list.
The Model Context Protocol is the open standard Anthropic released in late 2024 and the rest of the industry adopted in 2025. An MCP server runs as a separate process (or a hosted URL) and exposes tools. The AI client reads the tool list, decides which to call mid-conversation, and folds the result back into its reasoning.
Three things make MCP the strongest of the five methods.
It is live. Unlike Custom GPTs, MCP servers query the current state of your data every time. Your bookmarks today, your Notion this minute, your tickets from this morning. No upload step, no staleness.
It is yours. You can run an MCP server for any source you like. A folder on your laptop. Your personal database. Your bookmark collection. Anything with a useful API.
It is portable. The same MCP server connects to ChatGPT, Claude, Cursor, Windsurf, and Claude Code. Wire it once, use it everywhere.
The catch: Developer Mode is paid plans only. Full MCP with write tools is gated to Business and Enterprise. Pro and Plus users get read access, which covers the bookmark, notes, and document use cases nicely. Activation lives under Settings → Connectors → Advanced.
If you want a longer walkthrough, Add Your Bookmarks to ChatGPT via MCP covers the exact steps for the ContextBolt server.
How the five methods compare
| Method | Stores | Freshness | Plan | Best for |
|---|---|---|---|---|
| Saved Memories | Short facts | Live (you edit) | Free and paid | Personal preferences, working style |
| Chat history reference | Past conversations | Live (auto) | Plus, Pro | Continuity across sessions |
| Custom GPTs | Up to 20 files | Frozen at upload | Plus, Pro, Team | Fixed reference corpora |
| Apps | Curated services | Live | Paid, no EEA or UK | Notes, files, calendar, email in supported tools |
| Custom MCP servers | Anything you wire up | Live | Paid (Plus and up) | Your own data, your own tools, your own bookmarks |
Three patterns fall out of the table. Saved Memories is the only one that works on the free plan. Custom GPTs is the only one that holds files. MCP is the only one that gives you actual control over what gets connected.
How to pick the right method for your data
The honest answer is: stack them. The methods are not competing, they cover different shapes of memory.
Use Saved Memories for personal facts. “I prefer concise replies. I write in en-US. I run a SaaS called Acme. I have two kids and a dog.” Pin the things you do not want to retype in every conversation.
Turn on chat history reference. Free upgrade if you are on Plus or Pro. The retrieval is fuzzy but the safety net is worth it.
Use Custom GPTs for fixed reference material. A finished style guide. A frozen research corpus. A book you are working through. Anything you would treat as canonical, you upload once, never touch again.
Use Apps if your work tools are on the list. If your notes already live in Notion, Drive, or Box, and you are paying for ChatGPT, this is the lowest-effort path to making ChatGPT read them. If your tools are not on the list, skip this method.
Use MCP for everything else. Your bookmarks. Your local filesystem. Your personal database. Your saved articles. Anything that changes, anything that is not in OpenAI’s curated app list, anything you also want available in Claude or Cursor.
The version of ChatGPT memory most people experience (“it remembers I am vegetarian and not much else”) is the version that uses one of these five methods. The version that actually feels like a thinking partner uses three or four.
Where ChatGPT’s memory still falls short
A few honest takes worth saying out loud.
Saved memories drift. ChatGPT will save things you did not ask it to save, and forget things you did. The auto-save is opaque. Check what is in memory every few weeks (“what do you remember about me?”) and prune.
Chat history reference is fuzzy on purpose. The retrieval is not deterministic. The same prompt will sometimes pull in old context, sometimes not. Useful as a safety net, not as a primary memory layer.
Apps is regional and curated. If you are in the UK or EEA, this entire layer is dark. If your data is not in a supported tool, same outcome. OpenAI will widen the supported list and the geography over time, but as of mid-2026 the gap is real.
MCP is the most powerful and the hardest to discover. Developer Mode is hidden under Settings → Connectors → Advanced and ChatGPT will not nudge you toward it. The model never says “you could give me access to your bookmarks.” You have to know to ask.
There is also a pattern across all five methods that the marketing pages do not say out loud: ChatGPT’s memory is about what ChatGPT can ingest, not about what you have already saved. If you have spent years bookmarking content on X, Reddit, and LinkedIn, none of the built-in methods touch it. The platforms do not export to OpenAI. Your saved content lives in a wall outside ChatGPT.
This is the gap ContextBolt fills. ContextBolt is a Chrome extension that captures your X, Reddit, and LinkedIn bookmarks into a searchable AI knowledge base. The free tier ($0, 150 bookmarks) gives you AI tagging, topic clustering, and semantic search inside the extension. Pro ($6 a month) adds unlimited bookmarks, encrypted cloud sync, and a personal MCP endpoint. Wire that endpoint into ChatGPT via Developer Mode and your saved content becomes part of every conversation. Ask “what did I save about LLM evaluation” and ChatGPT calls search_bookmarks against your collection instead of guessing from training data.
The same endpoint works in Claude Desktop, Cursor, Windsurf, and Claude Code, which is the part that matters when you change AI tools every six months and do not want to redo your knowledge base. For the broader picture of what a personal AI memory stack looks like across clients, Personal AI Context Stack for Claude is the companion read.
The one opinion worth keeping
Most “how to make ChatGPT remember you” guides stop at Saved Memories. They tell you to type “remember that I am vegetarian” and call it done. That advice is fine for personal trivia and useless for anything else.
The real answer is that ChatGPT memory is a stack, not a feature. Saved Memories for the personal layer. Chat history for the continuity layer. Custom GPTs for the corpus layer. Apps or MCP for the live data layer.
If you skip the live data layer, you have an AI that knows your name and forgets every article you have ever read. If you wire it up, you have an AI that can actually act like it knows you. The difference between those two AIs is twenty minutes of setup.
Spend the twenty minutes.