OpenRouter Advisor, Ollama NVFP4, and Claude Fable Risks
Explore OpenRouter's new advisor, Ollama's NVFP4 performance boost, and the security risks of autonomous browser automation in Claude Fable.
Back to Feed
OpenAI has overhauled ChatGPT’s memory architecture, replacing the original “saved memories” system with a background process called “Dreaming.” This update addresses staleness, correctness, and scalability issues inherent in explicit, cue-based memory. For developers building on ChatGPT or analyzing its behavior, this shift represents a move from passive storage to active, continuous synthesis.
Dreaming V3 automatically curates memories by referencing chat history in the background, rather than relying on explicit user instructions. This allows the model to maintain context across multi-year time horizons and hundreds of millions of users. The system prioritizes freshness, continuity, and relevance. Memories are now reviewable via a summary page, allowing users to add, update, or suppress specific topics. This introduces a new layer of user control over what context is injected into future interactions, which is critical for managing hallucination risks and data privacy in enterprise deployments.
The update significantly improves three core capabilities:
OpenAI reports a 5x reduction in compute cost for serving Dreaming to Free users, enabling a broader rollout. Plus and Pro users in the US have immediate access, with Free and Go users receiving the update in the coming weeks. This infrastructure improvement suggests that long-context windows and memory retrieval are becoming more cost-effective to serve at scale.
Developers should note that memory synthesis is now a background process, not a deterministic API call. This means the context available to the model is dynamic and potentially opaque. When building applications that rely on ChatGPT for long-term user assistance, account for the possibility that irrelevant or outdated information may be synthesized and injected. The new memory controls offer a mitigation path, but the underlying retrieval mechanism is no longer strictly user-defined. This shift impacts how we design for consistency and auditability in conversational AI products.