Personal users
Individual users should verify whether this changes daily workflow value, free-plan limits, or the case for switching tools.
On June 12, 2026, OpenAI retired GPT-5.2 models (Instant, Thinking, and Pro) in ChatGPT. Existing conversations using these models automatically continue with their corresponding GPT-5.5 models. Additionally, new controls for memory summaries launched on the web, allowing users to delete displayed memories, turn off memory entirely, or edit memory text directly — with mobile rollout underway.OpenAI says memory updates are still rolling out across plans and countries, so availability may vary by account.
Users relying on GPT-5.2 should verify that their workflows function as expected with GPT-5.5. Those managing personalization or privacy through memory features should review the updated controls and consider using Temporary Chats where memory use is unwanted.
As announced in OpenAI’s official release notes dated June 12, 2026, GPT-5.2 models — including GPT-5.2 Instant, GPT-5.2 Thinking, and GPT-5.2 Pro — are no longer available in ChatGPT. Conversations previously using these models now continue using the corresponding GPT-5.5 models, which remain fully available. New memory summary controls are now live for all ChatGPT users on the web. Users can delete memories shown on the memory summary page or turn memory off entirely by selecting “Delete and turn off memory” from the three-dot menu. To edit memory content, users may type revisions into the text box at the bottom of the memory summary page or highlight and correct specific text inline. These controls do not delete past chats; re-enabling memory later may generate new memories from retained chat history. Temporary Chats remain unaffected by memory settings: they neither use existing memories nor create new ones. Memory features, including this update, are rolling out across ChatGPT plans and countries — availability may vary by region or subscription tier.
Individual users should verify whether this changes daily workflow value, free-plan limits, or the case for switching tools.
Creators should check whether the source changes output quality, usage rights, workflow speed, or public recommendations.
Developers should check API, model, integration, data handling, and migration implications before acting on this draft.
Teams should review pricing, admin controls, security, compliance, procurement, and rollout impact before publication.
After editorial review, update related tool profiles, review pages, comparisons, or update logs if this evidence changes selection guidance.