ChatGPT Dreaming V3: How OpenAI Rebuilt Memory From the Ground Up (June 2026)

Privacy Controls: What You Can Actually Do

OpenAI says users can view, edit, and delete their memory profiles directly. That access is real — it exists in ChatGPT settings under “Memory.” But there’s a catch worth knowing about.

With the old saved-memories list, every stored string was user-visible in plain text. You could read exactly what the model “knew” about you. Dreaming V3’s profile is a synthesized representation, not a verbatim transcript of what you said. The profile you view in settings is a human-readable summary of that synthesis, not a direct window into the raw data layer.

That’s not necessarily a problem, but it’s a meaningful difference. The old system was fully transparent by design. The new system offers transparency through a summary interface, which is not the same thing.

OpenAI moved to address this proactively. It published its Memory API and invited the Berkman Klein Center and the Electronic Frontier Foundation to independently audit the privacy guarantees. Early findings from those audits are reportedly favorable, but they’re not finished. The EFF review in particular — which focuses on whether synthesis introduces new inference risks beyond what users explicitly shared — is still ongoing as of the announcement date.

If you want no memory at all: that option still exists. Disabling memory completely in settings removes all synthesis and clears the existing profile. That hasn’t changed.

Rollout: Who Gets What and When

The June 4 rollout is US-only for Plus and Pro subscribers. OpenAI has been explicit about the sequence:

• June 4: Plus and Pro, United States
• Coming weeks: Free tier and Go subscribers, US
• After that: International markets, no confirmed timeline

The international delay is regulatory, not technical. Memory systems that synthesize and retain user data across sessions face different compliance requirements under GDPR and various national AI regulations. OpenAI is working through those approvals market by market.

For Team and Enterprise users: OpenAI hasn’t given a separate rollout date. Given that Enterprise contracts involve data retention commitments and SOC 2 / HIPAA considerations, expect a longer lead time there. The architecture is presumably compatible — the background synthesis process doesn’t need to change — but the compliance documentation does.

What This Means for Developers

Two things worth watching if you build on the ChatGPT API.

First, the Memory API. OpenAI has opened the API that manages user memory profiles to external access for vetted research partners. This is currently limited to the Berkman Klein Center and EFF audit specifically, not general developer access. But the existence of a Memory API suggests OpenAI is thinking about programmatic memory management as a feature. If that opens up more broadly, applications built on top of ChatGPT could read and write to user memory profiles directly — a fundamentally different capability than the current conversation-scoped context.

Second, the system prompt injection mechanism hasn’t changed. Memory still lands in the system prompt at inference time. That means applications using the API can still inspect what gets injected (if they control the system prompt layer) and can override or supplement it. The synthesis is new; the injection point is the same.

The practical implication: applications that relied on the predictability of the old saved-memories list — knowing exactly what strings were injected and in what format — may see behavioral differences. The synthesized profiles are more contextually dense but less structurally predictable than a list of user-managed strings.

The Trade-offs Nobody’s Talking About

Dreaming V3 is a good upgrade by most measures. But three things are worth examining honestly.

The audit trail problem. The old system’s weakness was accumulating stale memories. Its strength was full user visibility into exactly what was stored. Every memory was a string you wrote or approved. Dreaming V3 synthesizes inferences you never explicitly made. The profile you can view is a summary of that synthesis, not the synthesis itself. For most users this doesn’t matter. For users who are deliberate about data minimization — who want to know precisely what an AI system retains about them — this is a step backward in auditability, even if the performance is better.

Self-referential recall risk. The synthesis process reads across your full conversation history simultaneously. That means a pattern that appears across many conversations — even a temporary phase, a stress period, an unusual week — could get synthesized into a persistent memory that shapes future interactions. The temporal rewrite mechanism helps with clear before/after transitions (going to Singapore, changing jobs). It’s less clear how it handles gradual drift or temporary states that don’t have clean endpoint timestamps.

The metrics baseline. Going from 41.5% to 82.8% factual recall sounds dramatic. But OpenAI hasn’t published the eval methodology or the test set. A 41.5% baseline is unusually low — it suggests the old system failed more than half the time on recall tasks. Whether that baseline is representative of real-world use or a deliberately hard test set is unknown. The 82.8% figure deserves skepticism until independent researchers can replicate the eval.

None of this means Dreaming V3 is a bad product. The 5x compute reduction is real and has concrete consequences for accessibility. The temporal rewrite mechanism solves a genuine problem. The performance numbers, even with appropriate skepticism, represent real improvement. The trade-offs are worth understanding, not as reasons to distrust the upgrade, but because they define where the boundaries of the system actually are.

The Bigger Picture

Memory is now a serious technical differentiator in the AI assistant market. Google has been working on long-term personalization for Gemini through its UserContext system. Apple’s on-device processing approach to memory — which keeps synthesis local and avoids cloud inference costs entirely — is a direct architectural alternative to what OpenAI built.

OpenAI chose a cloud synthesis approach and got 82.8% recall at 1/5th the previous compute cost. Apple’s on-device approach offers privacy guarantees OpenAI can’t match but faces quality constraints from running on consumer hardware. Google’s UserContext is cross-product in ways that OpenAI’s per-ChatGPT memory isn’t. None of these is obviously correct — they’re genuine trade-offs between quality, privacy, and ecosystem scope.

What Dreaming V3 establishes: the compute cost of sophisticated memory synthesis is now low enough that it’s viable at free tier. That’s the inflection point. When memory becomes standard across all plan tiers, it shifts from a premium differentiator to table stakes. Every AI assistant without strong memory will look worse by comparison, not because the bar changed, but because users will have experienced what good memory feels like.

The rollout to free users over the next few weeks is the real story to watch. That’s where OpenAI establishes whether Dreaming V3 actually works at scale — not in controlled conditions with Plus and Pro users, but across the full distribution of ChatGPT usage patterns.