GPT-5

“A capable legacy flagship — the only real question is when to migrate and to which target, not whether.”

GPT-5 is a legacy flagship — still GA, still capable, but not the right choice for new builds. The strategic question for any team still on it is how soon to migrate and to which target: GPT-5.4 is the obvious quality-priority default (better capability, ~2x price), or GPT-5.4 mini for cost-priority workloads (better-than-GPT-5 coding at $0.75/$4.50). The chat-latest alias deprecation forces a 2026-10-23 deadline for teams using it; dated snapshots remain longer but won't see updates. The one durable reason to stay is fine-tuning, which the newer generation lacks. Plan the migration, don't drift.

“Its market is shrinking to fine-tuning and inertia — the newer generation owns the new-build narrative on both quality and cost.”

Strategically, GPT-5's market has narrowed to two pockets: teams that fine-tune (the 5.4/5.5 generation does not offer it) and teams whose migration cost exceeds the upgrade value. On the open market it has no competitive wedge — GPT-5.4 beats it on quality at ~2x price and GPT-5.4 mini beats it on coding at lower cost. Its positioning is purely transitional. Market timing has fully passed; it is a 2025 model competing in a 2026 frontier. Differentiation survives only in the fine-tuning niche.

“Genuinely cheap for the capability, but GPT-5.4 mini at $0.75/$4.50 with better coding is the comparison most migrations actually make.”

$1.25/$10 is genuinely cheap for the capability level, which explains the stickiness. Cached input drops 90%, Batch halves both sides. For high-volume backend pipelines, GPT-5 may still pencil out below GPT-5.4 base. But GPT-5.4 mini at $0.75/$4.50 with comparable-or-better coding is the real comparison — most cost-aware migrations move from GPT-5 to mini, not to GPT-5.4 base. The cost case for staying is shrinking; migration is the right financial call within a quarter unless fine-tuning ties you here.

“Recognizably the modern API shape, minus the modern tools — no computer use, no apply_patch. For code agents, that gap is real.”

Developers on GPT-5 recognize the entire current API shape — Responses, structured outputs, reasoning-effort dial. What's missing is the modern tool surface: no computer use, no apply_patch, no skills. For code-edit agents specifically, the move to the GPT-5.4 family is high-value because apply_patch is transformative for edits. SDK quality is identical to the current generation; promotion paths are clean. The chat-latest deprecation is the most concrete reason to migrate now — dated snapshots are safer but not future-proof. Fine-tuning support is the one thing developers would lose by moving.

“ChatGPT users no longer meet GPT-5 directly — where it surfaces in unmigrated apps it's good, but the stale knowledge shows.”

End users on ChatGPT no longer encounter GPT-5 directly — it has been replaced by 5.4 and 5.5 in default routing. Where it surfaces is in API-backed products that haven't migrated. Quality remains good for general chat; the 2024-09 knowledge cutoff occasionally surfaces in time-sensitive questions. Refusal patterns are slightly more conservative than the current generation. For most users the model is effectively invisible — they're getting GPT-5.4 or GPT-5.5 in ChatGPT and don't realize GPT-5 is still GA in the API.

“The launch-day SOTA headlines are 20 months old — quoting GPT-5's 2025 benchmarks today is the polite way to say 'don't build here.'”

The adversarial read: GPT-5's benchmark sheet is a 2025 time capsule. The AIME 94.6% and SWE-bench 74.9% were genuinely SOTA at launch, but GPT-5.4 nano — four tiers down and cheaper — now beats GPT-5 mini on coding, which tells you where the base sits. The model is still sold partly on launch-day prestige. The honest reasons to use it today are narrow and unglamorous: sunk-cost migration and fine-tuning. The alias deprecation (2026-10-23) is a forcing function the marketing soft-pedals. Nothing here is misleading — it's just an old model wearing its launch medals.