How to Check What ChatGPT's Memory Summary Leaves Out (2026 Guide)

ChatGPT's memory changed shape. The older system stored discrete items you had told it to remember. OpenAI replaced that with a synthesis, and it explained the reason for the change directly:

"The previous saved memories system often became stale and relied on users to manually manage updates. Memories could also contradict one another, such as 'I'm training for a marathon' and 'I sprained my ankle,' which made personalization less accurate."

That is a fair diagnosis and a real improvement for the everyday case. It also has a structural consequence. A synthesis is not a set of rows, so the summary can only ever be a rendering of it. OpenAI puts this plainly when asked whether the summary contains everything: "Not necessarily. ChatGPT's memory is based on a continually updated synthesis of context from your past chats, which may be broader than what can be shown as individual items in a summary." It adds that "some details may not appear in the summary, including when ChatGPT determines they are less relevant or not appropriate to show in this view."

Three practical consequences follow, and all three are documented.

An empty summary does not mean an empty memory. OpenAI lists the reasons a summary may not appear yet — a new account, memory recently enabled, or not enough chat history — and notes it should populate over time. There is also a manual nudge: from Settings, Personalization, Memory Summary, then Manage, the triple-dot menu offers a Refresh.

Deleting from the summary does not delete the knowledge. This is the one that surprises people most: "To fully delete something ChatGPT may know about you, you'll need to delete every source where it appears, including past chats, archived chats, files, the memory summary, and disconnect any connected apps that may contain that information."

Turning memory off is not a reset. OpenAI is explicit: "If you turn memory back on later, ChatGPT may create new memories from chats that remain in your chat history, including older chats."

So the summary is the surface of something with at least five inputs underneath it. If you have been treating it as the definitive answer to "what does it know," the gap between the two is exactly what this guide is about. The problem of an assistant confidently asserting something about you that you cannot find a source for is covered in why AI invents facts about you; this is the mechanism behind a milder version of it.

Reading the summary more carefully. Reasonable, and bounded by the thing OpenAI already told you: the summary is not everything. No amount of careful reading extracts what is not rendered.

Reverting to legacy saved memories to get a real list. This does work as a list, and OpenAI documents the route: from Settings, Memory, select the "saved memories" link below "Memory summary." You get discrete items again. You also get back the problems OpenAI named when it moved away from that system — staleness and contradiction — and you give up the synthesis. Worth doing deliberately, not as a workaround for wanting an inventory.

Deleting everything and starting clean. Then re-enabling memory later repopulates from chats that remain, per OpenAI's own note. Unless you also clear the chat history, this resets the summary rather than the knowledge.

Using the sources panel on each answer. This is genuinely useful and under-used: "You can see what sources were used to personalize a response such as custom instructions, past chats, files, and memories by tapping the book icon below the response." But OpenAI attaches a caveat — "Sources are designed to make memory easier to understand and control, though they may not show every factor or source that shaped a response" — and adds that "memory sources are not included in chats you share." Per-answer, not per-account.

Assuming Projects fence things off. Partly true, and only if project-only memory is what you are using. OpenAI describes that behaviour precisely: "chats can reference other conversations in the same project, but they cannot reference conversations outside the project, and chats outside the project cannot reference conversations in it." Useful as a scope, and a different thing from an inventory. Readers who expected projects to share memory by default will recognise the surprise from when ChatGPT projects don't share memory.

Hitting the ceiling and pruning. If you are on legacy saved memories and out of room, pruning is the standard advice and it silently changes what the assistant knows. That trade-off is covered in what to do when ChatGPT memory is full.

You cannot make the summary exhaustive. You can stop depending on it for the one job it is not built for — being the record — and you can verify the handful of facts that actually matter using the two checks OpenAI documents.

Step 1: Write down the facts you need it to know, as a list you control

Not everything. The load-bearing ones: your role and what you are working on, the conventions you have corrected it on more than once, the constraints that make its default answer wrong, the decisions you do not want revisited.

Most people find this comes to somewhere between fifteen and forty lines. That is the actual working set. Everything else in a year of chats is texture.

Keep it somewhere you can re-read and edit — a file, a doc, a memory layer — because the whole point is that this list does not depend on a rendering you do not control.

Step 2: Probe, using the method OpenAI names

OpenAI gives you the check in one line: "If you want to know if ChatGPT has remembered something, just ask in chat."

So ask, one fact at a time, in a normal chat rather than a Temporary Chat — OpenAI notes that "Temporary Chats do not use existing memories or create new memories," which makes them exactly the wrong place to test. Ask by contradiction where you can, because that produces a cleaner signal than a leading question. Instead of "do you remember that I prefer X," try asking for something where X matters and see whether X shows up unprompted.

Then check the receipt. Tap the book icon under the answer to see which sources it drew on — custom instructions, past chats, files, memories. When the answer is right but the sources panel shows nothing relevant, you have learned something useful: it got there from a chat, not from anything you can manage.

Work through your list this way once. It takes twenty minutes and it tells you which facts are actually live.

Step 3: Put the facts that must be explicit where explicitness is the contract

OpenAI draws a clean line between the two surfaces: "For explicit information or instructions, you can add it to your Custom Instructions. For information shared via conversations, ChatGPT can remember relevant details for you."

Anything on your list that has to be true every time belongs in Custom Instructions, not in memory. Memory is a synthesis that decides relevance; Custom Instructions are a statement you control. Use the summary's edit affordances for corrections — you can type a change into the box at the bottom of the summary, or highlight any text in it to correct that specific piece — but treat those as fixing a rendering, not as filing a fact.

The list from Step 1 is the durable asset here, and it should not live in the tool it is describing. MemoryLake holds it as an addressable layer: the facts, the reasons behind them, and a version history you can read, so "what does my assistant know" becomes a question with an answer.

Step 1: Create an API key

Sign in, open your workspace settings, and generate an API key. This is the credential your assistants use to read the same layer, so create it once and keep it available everywhere you work.

Step 2: Upload your first memories

Move your fifteen-to-forty lines across. One fact per entry, with the reason attached where there is one — "we bill in whole days because the finance system rejects partial days" survives a change of assistant in a way that "bill in whole days" does not.

Step 3: Connect your AI & agents

Connect ChatGPT, and whatever else you use. The facts arrive the same way in each, so the question stops being what the summary chose to render and becomes what you decided to record.

The first difference is that deletion becomes answerable. OpenAI's five-source list — past chats, archived chats, files, the memory summary, connected apps — is an honest description of a hard problem. When your working facts are held in a layer with an actual list, you can see and remove an entry there without a scavenger hunt, and the scavenger hunt inside ChatGPT is then only about the things you never meant to be durable.

The second is that contradictions become visible. OpenAI's marathon-and-sprained-ankle example is the perfect illustration of two true-at-different-times facts colliding. A synthesis resolves that silently and may resolve it wrong. A list you can read lets you catch it, which is the practice described in detecting conflicts in AI memory.

The third is that an empty summary stops being alarming. New account, recently enabled memory, or not enough history — OpenAI's three documented reasons — are all fine when the facts you depend on are not stored there in the first place.

The fourth is portability, which you will care about the next time you switch anything. Everything in this guide about ChatGPT's summary applies in its own dialect to every other assistant; the practical limits are catalogued in ChatGPT's memory limitations.

Probe in a normal chat, never a Temporary Chat. Temporary Chats do not use existing memories, so a negative result there tells you nothing.

Ask by contradiction. Set up a situation where the fact would change the answer, and see whether it does. Leading questions get you agreement, not evidence.

Read the sources panel, and believe its caveat. It shows custom instructions, past chats, files and memories for that response, and OpenAI says it may not show every factor. Use it as a signal, not a proof.

Refresh before concluding the summary is broken. From Settings, Personalization, Memory Summary, Manage, the triple-dot menu has Refresh. Try that before you start deleting things.

Keep the always-true facts in Custom Instructions. OpenAI positions that surface for explicit information and instructions. Relying on a relevance-ranked synthesis for a hard requirement is the wrong tool for the job.

Re-audit after any big project. A synthesis updates as you chat, and its timestamp tells you when — the summary shows when it was last updated. A project that changed your conventions is exactly when the old ones need correcting.

Do not put secrets in it to test it. Recording the decision is the goal; recording the credential never is, in any memory store. A broader pass over this is in auditing what your AI remembers.

OpenAI has been unusually straight about this: the memory summary will not include everything ChatGPT remembers, the way to check is to ask in chat, and fully removing something means clearing every source it appeared in. Those three sentences are not a complaint about the product. They are the operating manual, and most people have never read them.

Which means the fix is not to fight the summary. It is to stop asking a synthesis to be an inventory. Keep your own list of the facts that matter, verify them with the two checks the vendor documents, and put the ones that must always apply where the contract is explicit. Then the summary can be what it is good at — a quietly improving sense of who you are — without also being the only record of what you decided.