2026-09-17
ChatGPT holds first at 9.7, and the most useful item for ChatGPT subscribers this week sits in OpenAI's own changelog. On 14 September OpenAI announced that GPT-5.5 retires from ChatGPT, ChatGPT Work and Codex on 14 October, across every plan from consumer to Enterprise and Edu. The OpenAI API keeps it. Inside the apps, the replacement is GPT-5.6 Sol.
For most people this is a non-event, because the default model simply changes. The work is in everything that pinned a model by name. OpenAI's notice lists the places to check: workspace defaults, saved model settings, custom agents, scheduled tasks and scripts. If you set up a scheduled morning briefing or a custom agent over the summer, open it now and switch the model yourself. A task you test in September is a task that still runs on 15 October.
I keep ChatGPT at 9.7 because this is exactly how a platform should retire a model: a month of notice, a named successor and a checklist. Its ecosystem score of 9.7 reflects that maturity as much as the feature list.
Claude at 9.5 stays my pick for long writing and document work, with writing at 9.7 and coding at 9.7, both the best scores in this table. Gemini at 9.4 keeps reasoning at 9.7 and realtime at 9.5, and it is the assistant I use when the answer depends on something that happened this morning.
My practical advice applies to every assistant here. Keep one short document listing every automation you built on an AI chatbot, the model it uses and the date you last tested it. It takes ten minutes, and on retirement day it turns a surprise into a two minute fix.
Perplexity at 8.6 and DeepSeek at 8.2 stay where they are, and the ranking carries forward unchanged.
GPT-5.5 leaves ChatGPT on 14 October
OpenAI's changelog names GPT-5.6 Sol as the replacement in ChatGPT, ChatGPT Work and Codex. The API keeps GPT-5.5.
Check anything that pins a model
Workspace defaults, custom agents, scheduled tasks and scripts that select GPT-5.5 need a manual switch before the date.
A clean retirement supports the 9.7
A month of notice, a named successor and a checklist is how a mature platform handles change.
Keep an automation list
Write down each automation, its model and its last test date. It turns retirement day into a quick fix.