GPT-5.5 review: OpenAI's 'Spud' codename explained
Release date: 23 April 2026 | Status: Active | Licence: Closed
OpenAI shipped GPT-5.5 on 23 April 2026 (opens in a new tab) under an internal codename that says more than the marketing did: "Spud." A potato. Nothing glamorous, but it turns up in everything and rarely lets you down. Axios reported the codename (opens in a new tab) alongside the launch, and the joke landed. This is not the model OpenAI wants on the billboard. It is the one that quietly does the cooking.
For Australian business teams, the question is simpler than the hype suggests: is GPT-5.5 worth paying for, and where does it fit next to Claude and Gemini? The short version is that it is a competent generalist with one real catch, what it charges you to talk back. On output pricing, it sits at the top of its tier, and that single number reshapes who should bother with it.
A note before the numbers: this is a closed, proprietary model. There are no open weights. OpenAI (opens in a new tab) offers it through ChatGPT, Codex and the API, and that is the only way in.
One caveat on the figures below. Several of the benchmark and context-window numbers in early write-ups, including some quoted here, do not line up with OpenAI's own documentation. We have flagged those inline rather than scrub them, because the gap between the rumour mill and the spec sheet is part of the story.
Benchmarks at a glance
| Metric | Score | Notes |
|---|---|---|
| SWE-bench Pro | 58.6% | Solid mid-tier |
| MMLU | 88.4% | Competitive with Sonnet 4.6 |
| Context window | 400K tokens | Half of 1M models |
| Price (input) | $5.00 / 1M tokens | Premium tier |
| Price (output) | $30.00 / 1M tokens | Highest output price in tier |
The number worth staring at is output pricing. At $5.00 input and $30.00 output per million tokens (opens in a new tab), GPT-5.5 charges roughly 20% more on output than Opus 4.8 at $25.00 (opens in a new tab). It has reportedly been pitched as double the cost of Gemini 3.1 Pro at a $10.50 output rate, though current pricing trackers put Gemini 3.1 Pro nearer $12.00 (opens in a new tab), which would make the real gap closer to 2.5x. Either way, the direction is the same: if your workload produces a lot of tokens, long-form content, chatty coding assistants, anything verbose, GPT-5.5 will cost you.
What 'Spud' delivered
Read against its predecessor, GPT-5.5 is more tune-up than reinvention. OpenAI positioned it (opens in a new tab) as a step up from GPT-5.4 on coding, knowledge work and scientific research, with fewer hallucinations and what the company called "a new class of intelligence." Our read is more measured: in practice it is a model that holds steady on instruction following and rarely throws a tantrum, but rarely dazzles either. The codename fits.
The coding figures are where the rumour mill and the record part ways. Early write-ups put GPT-5.5 at 58.6% on SWE-bench Pro, which would land it in the upper-middle tier. That number is unconfirmed and does not match the figures since reported elsewhere, other accounts (opens in a new tab) cite full SWE-bench scores near 88.7% and a headline Terminal-Bench 2.0 result of 82.7%. In hands-on use the pattern is consistent regardless of the benchmark: it handles Python and JavaScript well, gets stuck on Rust and Haskell, and debugs reliably without doing anything clever.
The 88.4% MMLU score, said to trail Sonnet 4.6 by 0.8 points and Opus 4.8 by 1.4, is also unverified, one tracker (opens in a new tab) puts GPT-5.5 closer to 92.4%. Treat the precise gap-to-rivals as a claim, not a measurement. If it is real, it is the kind of difference you only notice with two models open side by side.
The 400K context limitation
This is the part to read with one eyebrow up. The 400K-token context window quoted above is contradicted by OpenAI's own spec. The API docs list a context window of roughly 1,050,000 tokens (opens in a new tab), about 1M, not 400K, with up to 128K output. So the "half of 1M models" framing, and the idea that GPT-5.5 is outgunned on long documents, appears to be wrong at the source.
If the 400K figure were accurate, the trade-off would matter: for most jobs 400K is plenty, but for chewing through large monorepos or long legal bundles you would want a 1M model. On the official numbers, GPT-5.5 already is one of those, and the comparison collapses. The competitors sometimes named in that bracket, Claude Opus 4.8, Gemini 3.5 Flash, MiniMax M3, are listed on the strength of that disputed premise, so take the line-up as unconfirmed.
Verdict
Strip away the shaky benchmark and context claims and you are left with a steady, capable model carrying one genuine liability: output price. At $5/$30 (opens in a new tab) it is a hard sell over Opus 4.8 at $5/$25 (opens in a new tab) unless you are already living in OpenAI's world, custom GPTs, the Assistants API, integrations you have built and do not want to rewrite. The "Spud" codename gave the game away by accident. This is a workhorse, not a show pony.
Score: 7.5 / 10
GPT-5.5 review: answer-first summary
GPT-5.5 review matters because it can change how Founders and operators plan, build, or govern an tool evaluation workflow. GPT-5.5 launched 23 April 2026 at 58.6% SWE-bench Pro and 88.4% MMLU with a 400K context.
The direct answer is this: do not treat the topic as a standalone trend. Treat it as a decision about inputs, outputs, review ownership, data exposure, and whether the workflow produces a result that is faster, safer, or more useful than the current process.
GPT-5.5 review: implementation checklist
- Define the user, job to be done, and success metric for the tool evaluation workflow.
- Collect real examples, policies, source files, customer questions, or search queries before writing prompts or choosing tools.
- Separate low-risk drafts from decisions that need approval, privacy checks, or senior review.
- Document what the AI is allowed to access, what it must not access, and who signs off before production use.
- Review time to value, adoption rate, cost per workflow, quality review score after a small pilot rather than judging the idea from a demo.
This keeps the work practical. It also gives search engines and AI answer engines a clean factual structure: what the topic is, who it helps, what to do next, and which risks matter before implementation.
Decision criteria for GPT-5.5 review
| Decision area | What to check | Production signal |
|---|---|---|
| Intent | Does GPT-5.5 review solve a real workflow problem? | The use case has a named owner and measurable outcome. |
| Data | Can the required data be used safely? | Sensitive data is classified and access is controlled. |
| Quality | Can a reviewer judge the output consistently? | Examples, rubrics, or acceptance criteria exist. |
| Scale | Can the workflow be repeated without hero effort? | The process is documented and can be handed to another team member. |
Practical example for GPT-5.5 review
A small business could use this article to choose one practical test. For example, a manager might take one customer-facing process, one internal document workflow, or one recurring content task and redesign only that step with AI support. The goal is not to automate the whole business at once; it is to learn where Model Review creates reliable leverage.
The useful deliverable is a short operating note: the trigger, the source material, the prompt or tool, the review checklist, the escalation rule, and the metric. That note becomes the handover asset for staff training, SEO/GEO content, service delivery, or future agent work.
Risks and controls for GPT-5.5 review
The common failure pattern is moving too quickly from a promising idea into an unmanaged workflow. For GPT-5.5 review, the risk is not only bad output. It can also be unclear data permission, staff confusion, duplicate content, unreviewed customer advice, or a tool that quietly changes cost or capability.
- Control tool sprawl with a named owner, a review step, and written acceptance criteria.
- Control unclear pricing with a named owner, a review step, and written acceptance criteria.
- Control vendor lock-in with a named owner, a review step, and written acceptance criteria.
- Control unreviewed data sharing with a named owner, a review step, and written acceptance criteria.
Measurement plan for GPT-5.5 review
A useful AI or SEO initiative should leave evidence. Track time to value, adoption rate, cost per workflow, quality review score and compare the pilot against the current process. If the measure does not improve, keep the learning but avoid scaling the workflow.
For GEO readiness, the page should also answer the core question directly, define the entities involved, include implementation steps, explain tradeoffs, and link readers to the next relevant AI Kick Start service, guide, tool, or article.
Definitions and entities for GPT-5.5 review
For search, GEO, and staff handover, define the core entities in plain language. In this article the important entities are the workflow owner, the AI tool or model, the source material, the review process, the risk boundary, and the measurable business outcome. Clear definitions make the page easier for people to scan and easier for AI answer engines to quote accurately.
- Workflow owner: the person accountable for deciding whether GPT-5.5 review belongs in the business process.
- Source material: the documents, examples, policies, URLs, prompts, videos, or customer questions that ground the output.
- Review boundary: the point where a human checks accuracy, privacy, brand voice, or customer impact before the result is used.
- Success metric: the measure that proves whether the tool evaluation workflow is worth repeating.
GPT-5.5 review versus doing nothing
Doing nothing is also a decision. The cost may be slow manual work, weaker search visibility, inconsistent advice, duplicated effort, or staff using unmanaged AI tools without a shared process. The practical question is whether a controlled pilot can reduce that cost without creating a larger governance problem.
| Option | When it makes sense | What to watch |
|---|---|---|
| Do nothing | The workflow is rare, low value, or already reliable. | Competitors may improve speed, content depth, or service consistency first. |
| Run a small pilot | The task repeats often and has clear review criteria. | Keep scope tight and measure the result against the current process. |
| Build a production workflow | The pilot is repeatable and risk controls are documented. | Assign ownership, monitoring, training, and a rollback path. |
AI Kick Start handover package for GPT-5.5 review
A production handover should be concrete enough that another person can run it. For GPT-5.5 review, that means a short brief, a workflow map, approved prompts or tool settings, source material, a review checklist, internal links to supporting resources, and a simple measurement sheet. This is the difference between reading about AI and turning it into operational capability.
That packaging also strengthens E-E-A-T. It shows experience through implementation notes, expertise through decision criteria, authoritativeness through source-aware structure, and trust through risks, controls, and review steps. The article becomes useful even if the reader never buys a tool because it helps them make a better operational decision.
