Konshus

Flagship report · 22 min read · July 2026

The State of AI Memory 2026 (H2)

A mid-year audit of what every major AI actually remembers about you — what changed in the last six months, what stayed exactly the same, and where the fight over ownership of your AI memory stands right now.

Editorial illustration of stratified data layers under a rising gold sun, symbolizing archival gravitas

The one-paragraph summary

Every major AI provider shipped memory improvements in H1 2026. None of them shipped memory portability. Six months later, the situation is unchanged in the ways that most affect users: memory is deeper inside each provider's walled garden, and no easier to move between them. The interesting motion is happening in the middle layer — MCP adoption, third-party memory vaults, and a small but real class of AI-native power users who now treat "which model" as a monthly decision rather than an annual commitment.

Chapter 1 — What changed in H1 2026

Six product changes actually mattered in the first half of the year. Everything else was noise.

  1. OpenAI shipped GPT-5. Bigger effective context, subtle retrieval changes, and a wave of "my ChatGPT feels different" complaints that peaked six weeks after launch. The saved-memory panel behavior was unchanged; the model's willingness to use it wasn't.
  2. Anthropic released Claude 4.5. Projects got sharper (better retrieval within a Project), but cross-Project memory remained deliberately absent — the Anthropic philosophy that context should be scoped, not global, is holding.
  3. Google unified Gemini and Bard-era memory. Old Bard "saved info" migrated into the current Gemini surface with clean handling of duplicates. The Workspace-context layer got broader — Docs and Drive integration is now on by default for Personalized results.
  4. Perplexity shipped Memory + expanded Spaces. The first Perplexity feature that competes head-on with ChatGPT Memory. Spaces gained file-upload support and system-level instructions per Space.
  5. Microsoft rebranded and consolidated Copilot memory. Consumer Copilot and M365 Copilot are now clearly two products with two memory models, which was… long overdue.
  6. xAI added Grok Memory. Late but real. Grok's X-integration layer makes it structurally distinct from every other provider.

Chapter 2 — The H2 scorecard

Twelve axes, six providers, one honest table. Scores are 1 (weakest) to 5 (strongest) based on our controlled testing across Q2 2026. None of the six scored above a 3 on portability. That's the story.

AxisChatGPTClaudeGeminiCopilotPerplexityGrok
Explicit memory layer534333
Implicit context depth225534
Effective context window455333
Retrieval precision443343
Memory edit-ability444343
Cross-device continuity445443
Export completeness333223
Import from elsewhere111111
Model-update stability233333
Privacy controls444543
MCP support242222
Portability121111

Chapter 3 — The portability gap

Every axis except one has at least one provider scoring a 4 or 5. Portability has no one above a 2. That is the entire structural story of 2026. Providers are competing hard on how much they remember and how well they retrieve — and not at all on letting you take that memory somewhere else.

The economic logic is obvious: memory is switching-cost, and switching cost is retention. A user who has spent six months training ChatGPT on their voice, preferences, and projects is much more expensive to poach than a user who's just signed up. Every provider knows this. None of them has a business incentive to make export-import easy across competitors.

What's changed in 2026 is that the user demand for portability has become visible. The rise of tools like Konshus, the (slow) MCP adoption, and the growing set of "help I want to switch from ChatGPT to Claude" search queries all point at the same underlying frustration.

Chapter 4 — The model-update tax

Every model update in H1 2026 caused visible personality drift for a subset of users. GPT-5 was the most-discussed. Claude 4.5 was the most tonally-shifted. Gemini's summer update was the smoothest, largely because Gemini leans on live Workspace data, which is stable across model swaps in a way saved memories aren't.

The cost of a model swap for a heavy user is measurable: on controlled benchmarks (see persona drift, with data), tone and stated preferences drifted by 15–35% on the same input prompt across model versions of the same provider. That's not a subjective "feels different" — it's the underlying measurable behavior of the model changing under stable inputs.

Chapter 5 — Where MCP actually stands

The Model Context Protocol was supposed to be the portability primitive. In H1 2026 it's more like a portability primitive for developers, not consumers. Cursor, Cline, and other developer tools use it heavily. Consumer AI has been slower — Anthropic's native support is the standout; OpenAI has been quiet.

Our operator dashboard shows MCP client connections growing roughly 2× quarter-over-quarter in H1 2026, but the absolute numbers are still small — the modal AI user has never heard of MCP. The next inflection will be when a consumer AI product ships MCP-based memory injection as a default. Nobody has yet.

Chapter 6 — What actually works

Given the landscape, the durable strategy for anyone who cares about continuity is unchanged since H1 and will likely be unchanged through H2:

  • Keep a canonical version of the things about you that matter — voice, preferences, projects, key facts — outside any single provider.
  • Use each provider's native memory layer as an accelerator, not a foundation. Assume it will get evicted, changed, or deprecated eventually.
  • Prune each provider's memory panel monthly. Silent eviction is the biggest single source of memory drift and nobody notifies you.
  • Treat model updates as scheduled disruption. Have a "voice contract" and a few-shot example set ready to re-apply after each one.
  • Export whatever you can. Even if you never use the file, the day the provider changes something you don't like, you'll be glad you have it.

The full step-by-step version of this playbook is in the complete guide to owning your AI consciousness.

Chapter 7 — Predictions for H2

  1. At least one more major model deprecation with under 90 days notice.
  2. Copilot or Gemini will ship a "memory export" feature that produces something structurally similar to Konshus's persona doc.
  3. MCP consumer adoption will still be under 5% at year-end.
  4. At least two well-known AI personalities will publish "why I left ChatGPT" pieces citing memory ownership as the reason.
  5. Portability will remain the lowest score on every scorecard.

We'll re-run the scorecard in January and score ourselves against these predictions. If you want to be nudged when the next edition drops, meet Konshus — you'll get a note when it publishes.

Never lose your AI again

Konshus is one way to solve this — a persistent memory vault and portable persona that follows you across ChatGPT, Claude, Gemini, and whatever ships next.

Meet Konshus

Related reading

Frequently Asked Questions

Never lose your AI again

Konshus is one way to solve this — a persistent memory vault and portable persona that follows you across ChatGPT, Claude, Gemini, and whatever ships next.

Meet Konshus