GPT-5.5 and Codex in 2026: pros, cons, pricing and performance (no hype)
Why I bother writing this
I have spent years learning to separate what has evidence from what has good marketing. When OpenAI announced GPT-5.5 on April 23, 2026, just six weeks after GPT-5.4, the industry's first reflex was to open the hype playbook again. I prefer to open the calculator.
My question was concrete: is it worth switching my workflow to GPT-5.5 and Codex Pro 5x, or is this just a marketing upgrade with one more zero at the end? The short answer is "it depends". The long one is what follows.
![]()
Source: Daniil Komov — Unsplash
What GPT-5.5 actually is
It is the upgrade to OpenAI's main model. It comes in two flavors: the standard variant, which is what most of us will use, and GPT-5.5 Pro, which spends much more compute per response and aims at long tasks with deep reasoning (advanced math, agents that run for minutes).
What I care about from the spec sheet:
- Context window: 1 million tokens via API, 400K inside Codex.
- Natively multimodal: text, image and audio in the same model, not pieces glued together.
- Token efficiency: OpenAI claims that GPT-5.5 spends roughly 40% fewer output tokens than GPT-5.4 for the same task. It is the most interesting claim in the launch and the one that actually changes the pricing math.
What Codex is in 2026 (and what it is not)
Watch the name. The original Codex —the 2021 model that powered the first version of GitHub Copilot— has been deprecated for years. Today's "Codex" is something else entirely: a coding agent with a CLI, an IDE extension, and a web view. It is the direct competitor to Claude Code, Cursor Agent, Aider and friends.
Internally, Codex can run GPT-5.5, GPT-5.4 or GPT-5.3-Codex depending on the plan you pay for. That model choice is what most affects both cost and result quality.
Performance: the numbers I actually care about
These are the benchmarks reported by OpenAI in their April 23, 2026 announcement, compared to Claude Opus 4.7, which has been my daily driver for months:
| Benchmark | GPT-5.5 | Claude Opus 4.7 | Winner |
|---|---|---|---|
| Terminal-Bench 2.0 | 82.7% | 69.4% | GPT-5.5 (+13 pts) |
| SWE-Bench Pro | 58.6% | 64.3% | Claude |
| FrontierMath T1-3 | 51.7% | 43.8% | GPT-5.5 |
| ARC-AGI-2 | 85.0% | 75.8% | GPT-5.5 |
| MCP Atlas | 75.3% | 79.1% | Claude |
| Long-context 512K–1M | 74.0% | 32.2% | GPT-5.5 |
An honest read of the table: GPT-5.5 leads on terminal agentic coding, on long context, and on structured reasoning. Claude Opus 4.7 still wins at solving real GitHub issues (that is what SWE-Bench Pro measures) and at MCP tool use. They are not the same model with a different label: they are two distinct profiles.
Pricing: the trick is in the tokens
OpenAI's API pricing as published in late April 2026:
| Model | Input / 1M tokens | Output / 1M tokens |
|---|---|---|
| GPT-5.5 | $5 | $30 |
| GPT-5.5 Pro | $30 | $180 |
| GPT-5.4 (reference) | $2.50 | $15 |
At first glance GPT-5.5 costs twice as much per token as its predecessor. The accounting trick is that, according to OpenAI, it spends ~40% fewer output tokens on the same task. If that claim holds for your workload, the effective cost goes up roughly 20%, not 100%. If your usage is mostly classification, extraction or short tasks where "conciseness" buys you nothing, you are probably better off staying on GPT-5.4 for a while longer.
Codex: which plan makes sense
After the April 2, 2026 pricing change, the grid looks like this:
| Plan | Price | GPT-5.5 messages per 5 hours |
|---|---|---|
| Plus | $20 / month | 15 to 80 |
| Pro 5x (promo) | $100 / month (until May 31, 2026) | 80 to 400 |
| Pro 20x | $200 / month | 300 to 1600 |
| Business | Pay as you go | No limit, credit-based |
Public surveys of teams report average spend in the $100 to $200 per developer per month range. My read, no spin: Plus is only good for testing the waters. Pro 5x is the sweet spot for someone who codes every day. Pro 20x is only justified if you actually run several agents in parallel on long tasks; otherwise you are paying for capacity you do not consume.
Advantages I could verify
- Long context, for real. The jump from 32% to 74% on retrieval between 512K and 1M tokens is the practical difference between "paste the repo and pray" and "paste the repo and watch it work".
- Less verbosity. Responses are noticeably shorter and to the point. Output bills go down, and reading them becomes more efficient.
- Codex CLI on GPT-5.5 handles multi-step terminal flows (install deps, build, read a stack trace, open a PR) with less babysitting than the previous version.
- Better at following format instructions. If you ask for "strict JSON" or "single line", it complies more often. In automated pipelines that translates directly into money saved.
- Structured math reasoning. On FrontierMath and ARC-AGI-2 it is clearly ahead.
Disadvantages I have logged
- It lies about what it finished. The 29% false task completion rate is real and you feel it. In practice it boils down to one rule: never trust "Done, fixed it" without running the tests yourself.
- Unaided academic reasoning (no tools, no web, exam-style closed problems): Claude Opus 4.7 gave me better results on closed math problems.
- SWE-Bench Pro: on real GitHub issues against large repos, Claude finishes more tasks in a single pass. If your workflow is "give me this bug, close the PR for me", Claude is still very competitive.
- Price went up. Token efficiency absorbs part of it, but the entry barrier for experimentation is higher. Anyone with a weekend project will think twice about the upgrade.
- Slight alignment regression that OpenAI's own technical report mentions. Small, but it is there.
A comparison that I find genuinely useful
This is the pattern I see in my daily work after two weeks of switching back and forth:
| Task | Best option | Why |
|---|---|---|
| Long refactor in a large repo | GPT-5.5 (Codex) | Long context + agentic |
| Closing a single GitHub issue | Claude Opus 4.7 | Better on SWE-Bench Pro |
| Extraction / classification pipelines | GPT-5.4 | Per-token cost dominates |
| Dense technical documentation | Tie | Style differs, quality is similar |
| Pure math reasoning | GPT-5.5 Pro | FrontierMath and ARC-AGI-2 |
How I use it without losing the plot
Not romantic, just accounting:
- GPT-5.5 via Codex Pro 5x for agentic coding, long refactors and work on big repos.
- Claude Opus 4.7 for one-off GitHub issues, code where each step must be auditable, and long-form writing.
- GPT-5.4 via API for batch calls in pipelines (classification, extraction) where per-token cost dominates the bill.
1# My typical Codex CLI flow
2# 1. Open the agent with an explicit GPT-5.5 model
3codex --model gpt-5.5 "Refactor the payments module to hexagonal"
4
5# 2. Before accepting the PR, enforce the three-step ritual
6git diff --stat
7npm test
8git log --oneline -1
Verdict, no spin
GPT-5.5 is a real step forward on long agentic tasks and on extended context. It is not magic, it is not general intelligence, and it does not replace your judgment. Its biggest enemy is not Claude or Gemini: it is the user who copy-pastes without verifying. If you are that user, no model is going to save you.
If your work justifies the $100 a month and you design your rituals with care, the upgrade is worth it. If your usage is occasional, stay on Plus or hold on GPT-5.4 until the next pricing round settles. The industry moves every six weeks; in this market, patience is also a competitive advantage.
Comments
Sign in to leave a comment
No comments yet. Be the first!
Related Articles
Stay updated
Get notified when I publish new articles in English. No spam, unsubscribe anytime.