GPT-5.1 and the return of the model picker
Instant and Thinking as named modes, adaptive reasoning, and personality controls. The router lesson got learned.
OpenAI released GPT-5.1 with two named variants — Instant and Thinking — plus adaptive reasoning that adjusts thinking time by question difficulty, and a set of tone presets.
Three months after removing the model picker caused a backlash, the picker is back with better names. That is a reasonable outcome and the intermediate lesson is worth stating.
the routing lesson#
The original GPT-5 design routed automatically and hid the choice. The intent was good — most users have no basis for choosing a model — and the execution exposed a real problem: when automatic selection fails, the user has no way to diagnose it or override it.
The user experiences "the model got worse." They cannot tell whether they hit a bad route, a degraded model, or their own bad prompt. There is no signal and no recourse.
5.1's approach — automatic by default, with named modes available — is the right shape. It is also exactly what every well-designed automatic system does: sensible defaults, visible state, manual override.
If you build anything that routes between models, ship the override. It costs one UI control and it eliminates an entire category of unfalsifiable user complaint.
adaptive reasoning#
The model adjusts thinking time based on assessed difficulty rather than applying a uniform budget. Easy questions answer immediately; hard questions get more compute.
This is a straightforwardly good idea and every provider is converging on it. The implementation question is calibration: a model that underestimates difficulty gives you a fast wrong answer, and a model that overestimates it burns money.
For API users, the practical guidance is the same as always: measure on your own task distribution. Adaptive reasoning is a good default and it is not tuned for your workload. If you have a task mix that skews harder or easier than average, set the budget explicitly.
the personality controls#
Tone presets — Professional, Friendly, Candid, Quirky, and others — plus finer adjustment of warmth and conciseness.
This got the most consumer coverage and it is the least technically interesting change. It is also a reasonable response to the fact that removing GPT-4o generated complaints about voice, not capability.
For developers, this is what a system prompt already did. The value is for consumer users who were not going to write one.
what I would actually check#
Whenever a point release lands, three things:
Instruction following on your specific format. Point releases change how literally the model follows formatting instructions surprisingly often. If you parse structured output, test it.
Refusal behavior. Safety tuning shifts between versions. If your application is in a domain that skirts a policy boundary — security research, medical information, legal content — re-run your test set. False refusals are a real production problem and they change silently.
Latency distribution, not average. Adaptive reasoning means variance. If you have a latency SLA, measure p95 and p99, not the mean.
the state of the frontier#
Three labs are now shipping point releases every few months rather than major versions annually, with capability differences that are small and getting smaller.
That is what a mature market looks like. The differentiation is moving to price, latency, ecosystem, and trust — and to the products built on top rather than the models themselves.
For anyone building applications, this is unambiguously good news. It means your model choice is increasingly reversible, and reversible decisions should be made quickly and revisited often.
— Dom, November 12, 2025