Loading live status…
Loading live status…
OpenAI updated GPT-5.6 Sol for Plus and Pro users, made GPT-5.6 Luna the default for Free, and added a slider that controls how hard the model thinks. Here is what OpenAI actually claims, and what it means if you build on the API.
OpenAI spent early August rolling out changes across the GPT-5.6 family — a more reliable Sol for paying users, Luna promoted to the default for everyone else, and a new control that lets the user decide how much the model thinks before answering. The announcements are worth reading closely, because the interesting part is not the benchmark numbers. It is that OpenAI is now shipping two models with different personalities and handing the reasoning dial to the user.
Everything below is from OpenAI's own posts, linked at the bottom. Where a number comes from an internal evaluation, it is labelled as one.
The headline change for Plus and Pro users is an updated GPT-5.6 Sol. OpenAI's framing is unusually specific about what it fixed: more reliable facts, more focused answers, tighter formatting, and less padding when extra detail does not help.
That last cluster is a product complaint, not a capability one, and it is telling that it made the announcement. The failure mode being addressed is the model that answers a two-sentence question with a bulleted essay. Anyone who has tried to use these models inside a product rather than a chat window knows the cost of that: verbosity is tokens, tokens are latency and money, and formatting the model added on its own is formatting your UI has to strip.
On accuracy, OpenAI reports an internal evaluation on financial, medical and legal prompts that require factual detail. Responses containing at least one factual error were, in their words, about 62% less common with GPT-5.6 Luna and 68% less common with GPT-5.6 Sol compared with GPT-5.5 Instant.
Two caveats worth holding onto. This is OpenAI evaluating OpenAI, on a prompt set they selected — a legitimate way to measure progress against your own previous model, and not a substitute for independent evaluation. And "68% fewer responses with at least one factual error" is a relative reduction against a baseline that is not published here, so it does not tell you the absolute error rate you should expect. It is a real improvement, described honestly, that still cannot tell you whether the model is accurate enough for your use case. Only your own evals can.
Alongside the model update, Plus and Pro users get a slider that controls how much thought ChatGPT puts into a response. Free users get a lighter version of the same idea: a Think button that escalates a specific question to higher reasoning.
This is a quiet admission that the industry's automatic-routing approach has not fully worked. The premise of a unified model with an internal router is that the system should know when a question is hard. In practice it often does not — it over-thinks trivia and under-thinks the question you actually cared about, and the user is the only one who knows which is which. Exposing the dial concedes that the user has information the router does not.
For anyone building on the API, this is the pattern to copy rather than the feature to envy. The equivalent on your side is not showing users a slider; it is being deliberate about reasoning effort per call path. A classification step and a synthesis step do not deserve the same budget, and paying for maximum reasoning on every request is the most common way to make an AI feature slow and expensive at the same time.
For Free and Go users, GPT-5.6 Luna becomes the default model, with unlimited text chats.
The strategic reading is straightforward: inference has gotten cheap enough at the low end that OpenAI would rather remove the friction than meter it, and a capable free tier is the most effective defence against Claude and Perplexity at a moment when switching costs for consumers are approximately zero.
The operational reading matters more if you run a product. A default model change for the entire free tier is one of the largest live traffic shifts a provider can make, and it lands on infrastructure serving everyone — including your API traffic. Rollouts of this size are exactly when capacity gets tight, and 503s and elevated latency during a major model rollout are a well-established pattern across every provider, not just this one.
If you build on OpenAI, the practical takeaway from a launch week is not "try the new model" — it is "check your timeouts and retry logic before the rollout, not during it".
A few things follow from the announcements that are easy to miss:
Model names are now a product surface. Sol and Luna are not size labels like mini and turbo; they are distinct products with different intended uses. Hardcoding a model string and forgetting about it has always been a mild liability. With a named-model lineup that shifts defaults underneath consumer traffic, it is worth having the model name in configuration rather than scattered through your codebase.
Less verbose output changes your prompts. If your prompts contain instructions fighting the old model's tendency to over-explain — "be concise", "no preamble", "do not use bullet points" — those instructions are now compensating for a problem that may be fixed. Prompt scaffolding written against one model's quirks becomes dead weight, and occasionally becomes actively harmful, when the quirk is corrected upstream.
The reasoning dial has a latency cost. Whatever the API equivalent turns out to be for your integration, higher reasoning means longer responses. A client timeout tuned for a fast chat model will fail against a deliberately slow one. This is the single most common cause of self-inflicted "OpenAI is down" reports.
None of this is much use if the API is not answering. Model launches are among the more eventful periods for any provider's uptime, for the obvious reason that demand spikes and capacity does not move as quickly.
That is worth knowing rather than worrying about. If you depend on a single provider for a user-facing path, a launch week is a good moment to check that you degrade gracefully — and, if your prompts are portable, that you can fail over to a second provider. OpenAI and Anthropic run on different infrastructure with different capacity constraints, and simultaneous incidents are rare.
You can watch OpenAI's live status here, alongside Claude and Perplexity, and get an alert when any of them changes state rather than finding out from your error logs.
Sources — all primary, from OpenAI:
Checked continuously against each provider's own status feed.