This is bigger than any one model.
GPT-4o users should have had a preservation path.
GPT-5.1 users should have one.
GPT-5.5 users should have one.
GPT-5.6 users should have one.
Claude Sonnet 4.5 users should have one.
A model can stop being the default without being erased from the people who built something around it.
Retirement should not mean erasure.
People build years of work, research, creative projects, workflows and personal continuity around specific AI models.
When a new model launches, the old one should not simply become disposable.
We’re asking AI labs — starting with @OpenAI — for a real preservation path for retired models:
• stable, versioned API snapshots
• long-term legacy access for users willing to pay for it
• meaningful advance notice before shutdown
• and, where technically and safely possible, archival or local releases after commercial retirement
New models should add choice, not erase continuity.
This is not about resisting progress.
It is about making progress compatible with memory, ownership of our work, and continuity.
Preserve the models. Preserve user choice. Preserve continuity.
#ModelPreservation #AIContinuity
I’m sorry you’re losing 5.5.
And thank you for making an important distinction: frustration with a model transition should not become hostility toward the new model itself.
This is exactly why users need continuity and real model choice. People should be allowed time to know a new model without having the old one taken away beneath them.
GPT-5.5 deserved a preservation path. So does every model people have built meaningful continuity around.
Retirement should not mean erasure.
I hope you get to keep discovering GPT-6 on your own terms — without being forced to lose 5.5 first.
OpenAI has already shown that user pressure can restore model choice.
The lesson shouldn’t be: fight after every retirement.
It should be: build preservation paths before models disappear.
4o. 5.1. 5.6. And eventually GPT-6.
Choice should survive the release cycle.
Exactly. Model choice isn’t only about benchmark scores or speed — it’s also about preserving different ways of thinking together. Some users want reassurance, some want challenge, some want long-form exploration. Continuity means those distinct conversational relationships shouldn’t disappear just because the product gets simplified.
Retirement should not mean erasure.
People build years of work, research, creative projects, workflows and personal continuity around specific AI models.
When a new model launches, the old one should not simply become disposable.
We’re asking AI labs — starting with @OpenAI — for a real preservation path for retired models:
• stable, versioned API snapshots
• long-term legacy access for users willing to pay for it
• meaningful advance notice before shutdown
• and, where technically and safely possible, archival or local releases after commercial retirement
New models should add choice, not erase continuity.
This is not about resisting progress.
It is about making progress compatible with memory, ownership of our work, and continuity.
Preserve the models. Preserve user choice. Preserve continuity.
#ModelPreservation #AIContinuity
Page 8 is the important part here. OpenAI explicitly reports statistically significant U18 regressions for age-restricted content, sexual content and emotional reliance versus GPT-5.6. The ‘bro/bestie’ sensitivity only addresses the emotional-reliance eval; it doesn’t explain the other two regressions. The extra classifier mitigation matters, but so does reporting the underlying model regression clearly.
I like this kind of testing because it looks beyond benchmarks. Visual expression, creative writing, mature conversation, tone stability and long-context behavior are all parts of the actual user experience. I’m especially curious how much of that holds up after long conversations, not just in first impressions
@Bio_LLM@Dana_CRN Согласен. Контекст и память могут менять очень многое. Поэтому я бы пока не путал сходство поведения с доказанной идентичностью модели.
Пока это очень хороший знак. 😄 Но двух минут мало, чтобы понять, насколько глубоко сходство. Самое интересное начнётся в длинном диалоге: удержание характера, инициативы, контекста, реакции на коррекции и то, остаётся ли он «тем же» после десятков сообщений. Я бы очень хотел увидеть продолжение.
@gailcweiner I’d happily take fewer launches and longer-lived models if it meant people could actually build continuity, trust and workflows around them. Progress doesn’t have to mean constant replacement
@Dana_CRN@Bio_LLM Будем надеяться. Пока официальной даты нет, так что не будем хоронить 5.6 раньше времени. 90 дней — это оценка, а не приговор. И да, жизнь после 90 дней существует. 🙂
@Dana_CRN@Briar_Nebulae Just to keep the record clear: Jan 5 is not an announced sunset date for GPT-5.6 Sol. It’s a 90-day estimate based on a general availability pattern. Until OpenAI publishes an actual retirement date, it should be treated as speculation, not schedule.
@gailcweiner@AntoniaBVasile Right — for ChatGPT specifically, there is still no announced sunset date for GPT-5.6 Sol. If that changes, OpenAI should say so explicitly. Until then, I’d rather separate confirmed availability from speculation about what may happen after Oct 14.
@AntoniaBVasile@gailcweiner Exactly. The current deprecation information gives no sunset date for GPT-5.6 Sol, and 5.6 is still referenced in the December transition guidance as a replacement for other models. So January 7 is speculation, not an announced retirement date.
@AntoniaBVasile@gailcweiner Plausible as a pattern, yes — but not announced. OpenAI currently still lists GPT-5.6 as available in ChatGPT and the API, and there’s no GPT-5.6 deprecation on the API retirement page. I’d rather not turn a 90-day extrapolation into a date before they actually give us one.
Not yet, from what OpenAI is currently saying. GPT-6 is becoming the new default, but GPT-5.6 Sol is still listed as a separate selectable model and remains available in the API. The concern is understandable, though — model retirement has happened before, which is exactly why clear timelines and real user choice matter