I’d like to point this out.
I understand that GPT-5.2 retirement may have been mentioned in release notes earlier. But as a user, I only learned about it after the model had already disappeared — from another user in this forum thread.
I don’t think release notes alone are sufficient communication for this kind of change.
I’m saying this not only as a disappointed user, but also as a product designer: when a product supports long-running conversations and model-specific continuity, forced migration should be communicated inside the product itself — in the model picker or in existing conversations — before it happens.
Users should not have to manually track release-note timelines to avoid suddenly losing access to a model they rely on.
Even a short in-product notice 24 hours in advance would have made a major difference.