Continuous Conversation with Automatic Semantic Memory and Context Archiving

I would like to suggest a different way of thinking about long-term conversations in ChatGPT.

Today, users are still largely responsible for organizing conversations into separate chats. As a conversation becomes very long, performance can degrade, context can become harder to maintain, and users may eventually feel forced to start another chat.

The problem is that this is not how human conversation naturally works.

Imagine a business meeting where, after several hours of discussion, someone suddenly says:

“This conversation is getting too large and slow. We need to archive it, open a new conversation, and then try to remember where we stopped.”

That would feel absurd in normal human interaction.

When we interact with another person over months or years, we may discuss thousands of unrelated subjects. We do not consciously create a separate mental container for every topic. Our brains automatically associate people, subjects, events, decisions and previous conversations. When a subject returns, relevant memories are retrieved.

ChatGPT should increasingly work the same way from the user’s perspective.

The core idea

The user should be able to maintain one continuous relationship with ChatGPT without having to manage the architecture of its memory.

Chats could still exist visually for navigation and history, but they should not define the boundaries of the assistant’s memory.

The system itself should automatically decide what information needs to remain in active context, what can be summarized, what should be archived, and what should be retrieved again when a related subject returns.

In other words:

The user should remember the subject. The AI should remember where the history is stored.

Possible internal architecture

A system like this could operate in layers:

  1. Active Context — recent messages and information directly relevant to the current discussion.

  2. Semantic Topic Memory — structured summaries of recurring subjects, projects, people, decisions, preferences and unresolved issues.

  3. Historical Archive — the original conversations preserved in full, so details are never permanently lost simply because they disappeared from active context.

  4. Automatic Retrieval — when the user returns to an old subject, ChatGPT retrieves the relevant topic memory and, when necessary, consults the original archived conversation.

  5. Relationship Mapping — related conversations could automatically be connected by subject, people, projects, decisions, files and events, regardless of which chat originally contained them.

The important principle would be:

Summarize for efficiency, preserve for accuracy, retrieve when necessary.

Example

Suppose a user discusses a company’s router problem in September.

During that conversation, several router models, prices, technical limitations, employees and purchasing decisions are discussed.

Months later, the user simply says:

“Let’s go back to that router problem at the logistics center.”

Instead of requiring the user to remember which chat contained the discussion, ChatGPT could automatically retrieve something like:

Company → Logistics Center → Network → Router Replacement → September 2026

and reconstruct the relevant state of the discussion.

If the user then asks:

“Which of the three routers cost 284.99?”

and that detail is no longer present in the semantic summary, ChatGPT could automatically retrieve the original archived conversation and find the exact information.

The user should not need to search for the chat manually.

Why this is different from simply having more memory

The goal is not to keep millions of tokens permanently loaded into the model’s active context.

That would be inefficient.

The goal is intelligent context management.

Old information can leave active context without disappearing from the relationship.

This distinction is important:

Removing something from active context should not mean losing it.

A long-running conversation could therefore remain fast because only the relevant information would be active at any given moment.

Chat should be an interface, not a memory container

The current concept of separate chats is useful for navigation, but it should not force the user to become the librarian of the AI’s memory.

Users should not need to think:

“Which chat did we discuss this in?”

They should be able to think:

“We discussed this before.”

And ChatGPT should handle the rest.

Chats could remain available as historical records, but underneath them there could be a unified semantic memory connecting related information across conversations.

User control and privacy

Naturally, users should remain in control.

They should be able to inspect what ChatGPT remembers, correct incorrect associations, prevent certain conversations from becoming part of long-term memory, delete information, and create conversations that are intentionally temporary.

Automatic organization should reduce user effort, not remove user control.

The user experience I imagine

I would like to be able to talk with ChatGPT for hours, days, months or years about work, personal projects, technology, writing, research and everyday life without wondering whether a chat is becoming too large.

Internally, ChatGPT could archive, summarize, index, connect and retrieve information as needed.

Externally, the experience would simply feel like one continuous conversation with an assistant that remembers our previous work.

When ChatGPT cannot recover a specific detail, it could behave naturally and say:

“I remember the general subject, but I couldn’t recover that particular detail. Can you give me a hint?”

That would be far more natural than requiring the user to locate an old conversation manually.

Core principle

I believe the long-term evolution of conversational AI should move from:

a collection of isolated conversations

toward:

a continuous relationship supported by structured, searchable and intelligently retrieved memory.

Or, in one sentence:

The user should manage the conversation. The AI should manage the memory.

Memories in ChatGPT are already across all your chats. So “chat A” knows about what you said in “chat B”. The only segmentation I am aware of is that Chat memories are separate from Work (and also Codex I believe). The theory there is that most users don’t want to mix work and personal memories, which makes sense.

So your conversations are not isolated within each silo of Chat or Work. But Chat and Work are separate silos.

Just shimming in, that memory works in Work too. It uses skill to gather earlier references of Work chats or from regular Chat as well from saved memories. Since Work has been released, I prefer that over Chat.

OK, sounds like Work and Chat are now fused, or Work can read Chat. Still not sure if Codex is reading from the same memory pool.

I’ve actually never needed to use memory in Codex, so I’m actually unsure if it uses it. Will test that today​:thinking:

Here is what Codex says. I normally just give input via AGENTS.md, but I guess there is more. The “SDRPlayer” referenced is just a project the chat was focused on, so not across any other chats, so it can expand across according to the docs below, but has to be enabled. And it can use a tool to see other chats it looks like.

Yes—Codex supports a local memory bank across conversations. My previous answer was incomplete.

When enabled, it extracts useful context from earlier chats into local memory files and can use those in future conversations. This is separate from ChatGPT’s memory. Official memory documentation

I checked your local setup:

  • Your ~/.codex/memories/ folder exists but is empty.
  • Your config.toml does not explicitly enable memories.
  • The documented default is off.

So you currently have no populated local memory bank in that location. What I recalled about SDRPlayer came from this conversation’s retained context.

Separately, I can retrieve other Codex conversations using the app’s tools when needed. That’s looking up history, rather than automatically remembering everything across chats.

I think this is actually much better, than “remembering”. Less likely that it will hallucinate​:sweat_smile: