ChatGPT Remembers You Now. Who Owns That Memory?

What ChatGPT memory actually does in 2026

Credit first, because the system deserves it. When memory is enabled, ChatGPT keeps a memory summary: a continuously and automatically updated synthesis of useful context from your chats, your uploaded files, and your connected apps (outside services like Gmail or Slack that you have linked to your account). You do not maintain it. It maintains itself. This replaced the older system of discrete saved memories, which OpenAI now calls legacy, precisely because a hand-curated list went stale and the automatic summary does not. You can view the summary, type corrections into it, refresh it, or delete it, all under Settings > Personalization > Memory.

It goes further than the summary. Projects have built-in memory: OpenAI's docs say a project remembers all the chats and files inside it, and a project-only mode walls that memory off so nothing leaks in or out. Scheduled tasks run on a timer, and on paid plans they can react to events, like a Gmail message or a GitHub pull request. ChatGPT Work handles longer multi-step jobs, and its cloud browser runs in the cloud, meaning on OpenAI's computers rather than yours, which means, in the docs' own words, a task "can continue in the background, including after you close your computer." In the desktop app, Work can even use local files (files on your own machine) and desktop apps with your permission.

That is a genuinely strong memory system. If someone tells you ChatGPT forgets everything, they have not used it recently. The honest questions start after you accept all of that.

Question one: can you see all of it?

OpenAI's Memory FAQ answers this directly, and the answer is no. The summary you can view and edit "will not include everything that ChatGPT remembers" based on your chats. Some details may not appear because ChatGPT decides they are less relevant, or not appropriate to show in that view. The memory sources indicator, a small book icon under a response, shows which sources personalized an answer, but the FAQ notes it may not show every factor either.

Deletion has the same shape. To fully delete something ChatGPT may know about you, the FAQ says you need to delete every source where it appears: past chats, archived chats, files, the memory summary, and any connected apps. Turn memory off and back on, and it can re-derive memories from whatever chat history remains. So you can edit what ChatGPT shows you it knows. What it knows and what it shows you are, by OpenAI's own description, not the same set.

Question two: can you take it with you?

ChatGPT has a real data export, meaning a downloadable copy of your account data: Settings > Data controls > Export, delivered within up to 7 days, link valid for 24 hours. The export docs say the ZIP contains "your chat history and other relevant account data." Custom instructions are explicitly confirmed as included. Scheduled tasks are explicitly confirmed as not included. And the memory summary is not listed at all. OpenAI's data-export docs do not say your memory ships in the export. Chat history does.

Portability is narrower still. The only transfer OpenAI documents is moving exported conversations between two ChatGPT accounts. The docs describe no way to move ChatGPT's memory of you to another model or another provider. To be precise about what that means: this is absence in the documentation, not proof of impossibility. But if a path existed, you would expect the company to document it, and it does not.

Question three: how much memory does your plan buy?

Memory depth is a pricing axis. OpenAI's own pricing page tiers it (a tier is a pricing level with its own feature set), in these exact words:

Read that column again. How well your assistant remembers you is a function of what you pay this month. Stop paying, and your memory drops a tier with you. The pricing page adds one more detail worth knowing: memory shares the context window (the fixed amount of text a model can consider at once) with your actual input, along with system instructions and internal processing. Memory of you competes for space with the thing you are currently asking.

Question four: where does it live?

Everything memory-touching in OpenAI's docs, the memory summary, project memory, scheduled tasks, Work tasks, the cloud browser, runs in OpenAI's cloud, not on hardware you control. The one documented local surface is the desktop app, where Work can use local files with permission and local chats stay on your computer. That is worth crediting. But even there, the assistant and its memory of you live on OpenAI's side. The docs describe no local or self-hosted deployment of ChatGPT or its memory, and no mechanism for an agent on your own machine to read what ChatGPT remembers about you. There is not even an API for custom instructions; the FAQ says one is not coming.

None of this is a scandal. It is the normal shape of a cloud product. It just means the memory is theirs to render, theirs to tier, and theirs to keep.

The other shape: memory as files you own

There is a second way to build an assistant that remembers you, and it is the one we teach. The memory is plain text files on your own machine. An instruction file describes who you are and how you like to work; the assistant reads it at the start of every session. Memory files hold what it has learned: decisions, preferences, project state; it writes to them as you go.

The properties fall out of the substrate. You can open every file in a text editor and read all of it; there is no summary view deciding what is appropriate to show. You can edit any line directly. You can copy the folder to a new machine, back it up, or put it under version control. And because the files are just text, they are not welded to one vendor: point a different model at the same files and it knows you on the first message. Memory bounded by your disk, not your plan. Agentic tools like Claude Code and OpenCode already work this way out of the box, and you do not need to be a developer to run them. If you are weighing the wider market of memory products against building, the buy-or-build guide covers that decision on its own.

Which one should you keep?

Honestly: maybe ChatGPT. If you want zero setup, polish, and a memory that maintains itself, ChatGPT's tradeoff is a reasonable one, and nothing above should scare you off it. Keep it, glance at your memory summary now and then, and know that the export covers your chats but not the memory itself.

Ownership matters for a different reader. You want to read everything your assistant knows about you, not a curated view. You expect to switch models as they leapfrog each other, and you want your accumulated context to survive the move. You are building something over years and do not want its memory rented by the month. If that is you, the file-based shape is not a compromise; it is the point. It costs effort ChatGPT does not: you install tools, follow instructions, and make decisions while your agent does the technical work. That effort buys you a memory nobody can tier, summarize, or hold.