AI products have long been trying to solve a practical problem: how to make users repeat themselves less without becoming progressively worse at understanding what they want now.

For individuals, the problem is easy to recognize. Every new conversation requires another explanation of who they are, who an article is for, how far a project has progressed, and what style the answer should use. The AI may have been used many times, yet every session can feel like reinstalling and configuring it from scratch.

Enterprises face an amplified version of the same problem. Employees cannot paste company policies, project documents, customer context, and internal terminology into every question. Team handoffs cannot depend on chat histories saved by one person. For AI to become part of a real workflow, it needs some form of continuity.

Products therefore began moving from “understand this conversation” to “remember what we discussed before.” This makes AI appear smarter and more familiar with its users, but it introduces another difficulty: the system may not merely remember the past; it may become anchored to it.

1. If Every Session Starts with an Introduction, AI Is Still a Disposable Tool

The absence of cross-session memory does not mean a model cannot understand the previous message. It can usually continue a discussion within the current chat. The difference is that the context and shared understanding established there do not automatically follow the user into a new conversation.

For looking up a fact, translating a passage, or solving a calculation, starting over has little impact. Once a task lasts days, weeks, or months, however, repeated explanations become a real cost. Users must restate the goal and explain what has been completed, which approaches were abandoned, which file is current, and which earlier conclusions remain valid.

Many people respond by saving a fixed prompt that describes their role, tone, formatting preferences, and working requirements, then sending it at the start of each session. This is simple and gives the user explicit control over how the AI should respond, but it still feels more like configuring a tool than continuing a collaboration.

Nor should Chinese mainland model platforms be treated as though they all lack memory. Products are at different stages. Kimi, for example, publicly offers a cross-session “memory space” that selectively stores preferences, habits, and style, and lets users view, edit, or delete those memories. The meaningful differences therefore come from individual products and settings, not simply geography.

From an individual user's perspective, however, having to repeat the same prompt does make AI feel less intelligent. A model may have strong reasoning and writing abilities while remaining unaware of what the user explicitly rejected last time or where a long-running project currently stands. The model is capable, but the experience lacks continuity.

Cross-session memory first addresses this repeated return to zero.

2. When “Understanding You Better” Becomes “Speaking for Your Past Self”

With cross-session memory, a new conversation is no longer a completely blank page. A system can retain the user's usual language, preferred response style, long-term goals, and selected historical information, then apply those details to later answers.

ChatGPT currently separates memory into saved memories and references to past chats, with controls for each. Newer memory systems are also adding abilities such as editing summaries, lowering the priority of certain information, and viewing earlier versions. Gemini can likewise personalize responses with past chats. Users can turn the feature off or delete historical conversations to reduce the chance that particular information will continue to be referenced.

These features move AI from “meeting you again every time” toward “gradually forming an understanding.” The problem is that understanding easily becomes a summary, and a summary can harden into a fixed view.

Language, forms of address, and typical answer length are relatively stable and often suitable for long-term storage. A person's opinions, project direction, and writing needs are not. A past preference for short answers does not mean a current research report must be short. Using a particular technology before does not mean a project still uses it. An article that began from a technical perspective may later shift toward individual or enterprise users.

If a system remembers only “what the user likes” or “what the project uses,” without retaining time and scope, it can turn a one-time choice into a permanent label. The AI appears to understand the user increasingly well, while in reality it may only be growing more familiar with a profile formed in the past.

That familiarity also changes how users judge its answers. A model with no background knowledge is easy to catch when it is wrong. A model that can accurately name the project, describe the user's writing habits, and recall an early plan is more likely to be trusted even when it cites an obsolete state.

The risk of memory is therefore not limited to remembering one fact incorrectly. It can also mean continuing to interpret a person who has changed as though they were still their former self. The user changes direction, but the model treats the new request as an extension of an old preference. An abandoned approach keeps returning because it was discussed frequently in the past.

AI can thus move from one extreme to another: from not knowing the user well enough to knowing the past too well and struggling to accept that the present is different.

3. New Chats Know Too Little, While Old Chats Know Too Much

To avoid explaining everything again, some users continue working in the same old conversation. It contains the complete discussion, files, and revision history, so it appears more reliable than starting a new chat.

But a longer conversation does not guarantee that the model understands the current state more accurately.

Context can be understood as the working material a model receives for one answer. Chat history, uploaded files, tool results, and information supplied by the system all enter this temporary workbench in some form. A larger context window can hold more material, but a model does not read every part with the stable, equal precision of a database.

The Lost in the Middle research found that models generally use important information more successfully when it appears near the beginning or end of a long context; performance can fall when the same information is placed in the middle. Microsoft's research on multi-turn conversations found that tested models performed an average of 39% worse across six task categories than in single-turn settings. Models tend to make assumptions early and commit prematurely to a solution path. Once they go wrong, later recovery is often difficult.

This closely matches a common user experience: the model remembers the original goal and can repeat the latest requested change, yet misses the decision in the middle that actually changed direction. It says that it understands, then continues using the old structure.

As a conversation grows, products may summarize or compress it to reduce context usage. A summary can preserve the general subject while losing the sequence of state changes. Suppose the original discussion was “propose approach A, test it, discover a problem, abandon A, and switch to B.” A summary may retain only “discussed approaches A and B.” Both names survive, but it is no longer clear which one was rejected.

Public issue reports show similar experiences. One VS Code user said that after Copilot Agent displayed “Summarized conversation history” during a long debugging session, it lost a clue it had already found and entered a repetitive loop. Another Codex user reported that after automatic context compaction, the assistant switched from the current task back to an old task that had already been completed and performed an unrelated git push.

These are reports about specific product versions and do not prove that every product fails in the same way. They do show that a complete chat remaining visible in the interface does not mean the model received the same complete working scene for its current response.

Individuals are therefore caught in a dilemma. A new chat lacks background. An old chat carries inertia from early judgments. Cross-session memory reduces repeated explanation but may transport an outdated understanding into the new conversation.

4. An Organization Does Not Need an AI That “Remembers Every Employee Chat”

Enterprises also need continuity, but enterprise memory cannot simply be personal memory at a larger scale.

An individual may ask AI to remember a preferred name, writing habits, or interests. What an enterprise needs to continue are product definitions, customer conditions, project states, operating procedures, and formal policies. These come from different sources, carry different permissions, and have different effective states. Their status cannot be determined solely by whether they appeared in a conversation.

Current product designs reflect this distinction. Gemini's personalization based on past chats is not available for work or school accounts. ChatGPT Enterprise lets administrators control workspace memory, but “reference chat history” is not currently offered to Enterprise and Edu in the same direct way as individual plans.

This shows that the consumer promise of “gradually understanding you” cannot simply be copied into an organization. One employee's discussion cannot automatically become team memory, and a personal preference cannot be mistaken for an organizational rule.

When an employee says, “We could consider approach A,” it may be only an opinion. A process mentioned in meeting notes has not necessarily been approved. A document highly relevant to the current question is not necessarily the version currently in force.

If AI compresses all of this into “what the company said before,” individual judgments, test proposals, and formal decisions can become mixed together. The system acts as though it understands the organization deeply while failing to distinguish who has authority to decide or which record is effective.

Enterprises therefore need to separate at least several kinds of information: an employee's personal work context, a team's shared project state, and approved organizational knowledge. All can help AI answer, but they cannot carry the same weight.

5. Being Able to Find Something Does Not Mean It Is Still Valid

Enterprise knowledge systems usually provide AI with background through document libraries, email, meeting records, business platforms, and databases. This is clearly more efficient than copying material manually, but retrieval solves only “can the system find it?” It does not automatically solve “should the system use it now?”

Microsoft 365 Copilot uses Microsoft Graph and supplied files to provide organizational context while respecting the user's existing data-access permissions. This helps prevent employees from using AI to bypass established permissions, but another problem remains: permission to read a file does not make that file the current authoritative version.

A single project may contain drafts, test versions, historical copies, and a formal release. Customer requirements may have changed while old email remains. A production process may have been updated without the old operating document being deleted. If AI retrieves material using only keywords and relevance, it may very accurately find something that is no longer valid.

Enterprise connectors also use different modes. Microsoft's current documentation distinguishes synchronization connectors, which periodically index external content into Microsoft 365, from federated connectors, which query an external system at answer time. The former supports unified search but depends on an indexing schedule. The latter is closer to real-time data but still depends on the source system's content and permissions being correct.

Incorrect permission settings create another risk. Microsoft explicitly warns that configuring a connector as visible to everyone in an organization can expose sensitive content too broadly.

Enterprises therefore have to solve more than memory. They must manage versions, permissions, timeliness, and approval state. AI can find history, but history should not continue to represent the organization's present decision merely because it still exists.

6. A Side Path: Why AI Progressed Toward Cross-session Memory

The problems individuals and enterprises face today follow from the development path of AI products.

The initial direction was straightforward: expand context so the model could see more at once. Anthropic increased Claude's context from 9K to 100K tokens in 2023. When Google introduced Gemini 1.5 Pro in 2024, it tested context windows of up to one million tokens with selected developers and enterprise customers.

Longer context did not automatically solve information use. Anthropic later specifically advised extracting relevant quotations before answering questions about long material in order to improve recall.

As context continued to grow, products added summaries, retrieval, project knowledge bases, and external connectors. Instead of placing the entire history into the model every time, the system first selected material that might be relevant and then inserted it into the current context.

Cross-session memory can be seen as the consumer-facing continuation of this path. It is not a second brain operating independently of context. Before an answer, the product selects information from past chats, memory entries, or external sources and places it back onto the current workbench.

This explains why context problems and cross-session memory problems converge. An old conversation may lose the sequence of changes during compaction, and a cross-session system may then place the surviving conclusion into a new conversation. Public evidence is not sufficient to show that every product saves conversation summaries directly as long-term memories, but both capabilities ultimately face the same question: when past information enters the present answer, how does the system determine whether it is still valid?

7. The Hard Part Is Not Saving; It Is Letting Go

Individuals and enterprises should not have to choose only between “remember nothing” and “remember everything.”

With no memory, individuals repeatedly restate prompts and employees repeatedly copy organizational background. With total memory, temporary opinions, old project states, and obsolete files may continue shaping later answers.

Better memory must handle three things at once: continuity, letting go, and correction.

Continuity allows stable background to keep doing useful work. Individuals should not have to restate their language and long-term goals every time, and enterprises should not have to repeatedly explain established terminology and approved policies.

Letting go does not mean deleting all history. It means removing invalidated content from the current task. A system can preserve the fact that a user once adopted a writing style or that a company once tested a process, but it should not assume that either remains valid merely because it was once correct.

Correction cannot consist only of a model saying “understood” in its current response. When an individual changes a preference, a project changes direction, or an enterprise releases a new version, the new state should genuinely influence later answers. Old content can remain as history, but it must be clearly marked as no longer being the current conclusion.

Products are adding controls to view, edit, delete, and disable memories, showing that vendors recognize memory cannot be write-only. Kimi lets users inspect, update, and delete memories. ChatGPT and Gemini offer different levels of memory management and ways to turn the capability off.

Controls alone cannot solve the entire problem. Users may not know which historical detail influenced an answer, and an enterprise may not know why an obsolete file was retrieved. AI also cannot observe changes in the real world that no one has told it about.

Mature memory should therefore not claim to possess the latest state forever. It should distinguish stable information, the last known state, and facts that remain unconfirmed. When an obvious conflict appears, it should not silently choose the past. It should expose the conflict and ask the individual or organization to confirm what is current.

Memory needs a way to change

Memory reduces repeated explanations, but outdated preferences and project information can keep steering new answers. In an organization, incorrect context or permissions can also affect customer communication and project decisions.

A useful memory system must retain what is still valid, let users correct or remove what has changed, and reflect those corrections in later answers. Its value depends on the accuracy and relevance of what it remembers.