OpenAI Codex just got a lot bigger than “an AI coding agent”
OpenAI is turning Codex into an async engineering workspace that spans the app, IDE, terminal, browser, pull requests, Slack, and scheduled background work. That changes the buying question from “is this a code helper?” to “is this the best place to run developer work in parallel?”
OpenAI has been shipping Codex in waves for a while, but the latest rollout is the first time it feels like one product instead of a scattered set of coding surfaces. The official positioning now stretches from the desktop app to the IDE extension, CLI, web, GitHub reviews, Slack, in-app browser, and computer use on macOS. That is a much bigger story than “better code generation.” It is OpenAI making a grab for the operating layer of engineering work.
What changed in OpenAI Codex?
The headline changes are concrete. OpenAI says Codex now works in the app, IDE, terminal, web, GitHub, iOS, and Slack. Recent upgrades bundled a new GPT-5.3-Codex model for agentic coding, a rebuilt CLI, an IDE extension for VS Code-compatible editors, faster cloud task performance via container caching, automated code review, an in-app browser for rendered pages, and computer use for macOS apps. April 2026 added three more shifts: a token-based credit billing model, a new $100 Pro tier with up to 10x Plus usage, and a research preview of GPT-5.3-Codex-Spark – a smaller, real-time coding model that targets more than 1,000 tokens per second. Together these push Codex toward general digital work rather than pure code output.
| Change | What OpenAI shipped | Why it matters | Operator take |
|---|---|---|---|
| Unified Codex experience | Same ChatGPT-linked product across app, IDE, CLI, web, GitHub, Slack, and mobile | Less tool-hopping and better continuity across local and cloud work | The real platform move. OpenAI wants the workflow, not just the model call. |
| GPT-5.3-Codex (+ Spark) | Default cloud model for long-horizon engineering and code review; Spark is a near-instant variant in research preview for Pro | Higher reliability on bigger tasks, and a real-time model for tight inner-loop work | Framing this as “more reliable async execution plus a fast inner loop” lands better than “smarter model.” |
| IDE extension | Works in VS Code, Cursor, and other VS Code forks | Codex meets developers where they already work | This makes Codex competitive inside competitor territory instead of requiring its own habitat. |
| In-app browser | Shared rendered-page view for local or public pages without sign-in | Better web debugging and design feedback loops | A quiet but important wedge into front-end review, QA, and iteration. |
| Computer use (macOS) | Can see and operate macOS apps with permissions; not available in EEA, UK, or Switzerland at launch | Expands from code tasks into GUI verification and multi-app workflows | This is the moment the “coding agent” story becomes too small. |
| Automations + PR workflow | Thread automations, GitHub review hooks, scheduled work, chat threads without project folders | Makes Codex feel like a background teammate | The strongest commercial angle is not speed alone. It is unattended throughput. |
| Token-based credits | From April 2, 2026, Codex usage is billed in credits per million input, cached-input, and output tokens; Fast Mode doubles consumption | Clearer, API-aligned cost control instead of opaque message counts | This simplifies cost-of-ownership modeling and makes Codex directly comparable to raw API spend. |
Why this update matters for developers
The short version: Codex is no longer asking for a seat next to your editor. It is asking to become the place where tasks start, branch, verify themselves, and get reviewed. That is a different purchase. For individual developers the question is still “does it help me ship today?” For teams the question is becoming “should Codex own the queue of low-to-medium-risk engineering work that previously sat in a backlog nobody got to?” Those are related but not identical decisions, and the right answer depends on how much of your work is async-friendly.
Codex is no longer just an AI coding model. OpenAI is turning it into an async engineering workspace that can plan, review, verify, and operate across tools. If your team’s bottleneck is throughput on bounded tasks rather than single-file autocomplete, that matters more than any benchmark score.
OpenAI Codex pricing in April 2026: the real angle is distribution, not just dollars
OpenAI’s smartest pricing move is not a headline discount. It is bundling Codex into ChatGPT plans people already understand. The company says Codex is included with ChatGPT Plus, Pro, Business, and Enterprise/Edu, with temporary availability in Free and Go and different limit multipliers by plan. Plus is the low-friction trial path at $20. Pro now splits into a new $100 tier built for longer, high-intensity sessions (up to 10x Plus Codex usage during the launch promo) and a $200 tier for heavier parallel work. From April 2, 2026, any usage beyond bundled limits is billed in credits per million input, cached-input, and output tokens, with cached input discounted roughly 10x and Fast Mode doubling consumption. That makes Codex easier to sample than a new standalone tool, while still leaving a clean overage path when teams outgrow the bundle.
| Tool | Official entry price | Best fit | What stands out right now |
|---|---|---|---|
| OpenAI Codex | Included with ChatGPT Plus ($20); Pro tiers at $100 and $200; token-based credits beyond bundled limits | Teams already inside ChatGPT who want cloud tasks, PR review, browser verification, and cross-surface continuity | Distribution advantage: easier to trial if you already pay for ChatGPT. |
| Cursor | Pro $20, Pro+ $60, Ultra $200 | Developers who want the strongest all-in-one editor experience with cloud agents | Still the cleanest “AI-native editor” framing in the market. |
| Windsurf | Free, Pro $20, Max $200, Teams $40/user | People who want model access breadth and a familiar quota model | Very aggressive free-to-paid ladder. |
| GitHub Copilot | Pro $10, Pro+ $39 | Developers deep in GitHub who want lower entry cost and integrated coding help | Cheapest serious paid entry, but premium agent delegation sits higher up. |
| Claude (incl. Claude Code) | Pro $20 monthly / $17 annualized, Max from $100 | People who prioritize writing quality, reasoning, and flexible collaboration with Claude Code included in paid tiers | Very strong at UI/UX thinking and code explanations, but pricing becomes heavier for power users. |
Codex vs Cursor vs Claude Code vs Windsurf vs GitHub Copilot
Right now the cleanest way to compare these tools is by operating style, not benchmark theater. Cursor still owns the “native AI editor” mindshare. Claude Code still wins a lot of affection for UX, creative problem-solving, and front-end taste. GitHub Copilot stays dangerous on price and distribution. Windsurf keeps pressure on quotas and model access. Codex’s new wedge is different: async execution plus workflow spread. It wants to be the tool you start in ChatGPT, continue in the editor, verify in a browser, and hand off to PR review without changing systems. Many experienced teams are ending up with a stack – Claude Code for architecture and ambiguous work, Cursor for the daily editor loop, and Codex for background refactors and PR hygiene – rather than a single winner.
Choose Codex if…
You want async cloud tasks, integrated PR review, ChatGPT-linked access, browser verification, and the ability to move between app, IDE, and terminal without switching products.
Choose Cursor if…
You live in the editor all day and care most about the strongest AI-native IDE workflow with clear paid tiers and cloud agents.
Choose Claude if…
You need better design sense, stronger writing, and a more conversational planning style, especially for UI-heavy or ambiguous tasks.
Choose Copilot or Windsurf if…
You care about lower-price entry, existing GitHub gravity, or a simpler ramp with broad model support and less interest in the full ChatGPT ecosystem.
Early reviews of the new Codex: what people like and what they complain about
The early reaction is not a clean victory lap. The strongest praise themes are precision, context discipline, parallel tasking, and usefulness on smaller backlog work that would otherwise sit untouched. The strongest complaint themes are speed, awkward UX, permissions friction, usage limits, Windows rough edges, and weaker instincts on UI-heavy work. Codex is becoming more valuable, but the operator experience is still uneven.
Users praise: steerability
Developers say Codex follows instructions with unusual precision and tends not to improvise unwanted changes.
Users praise: parallelism
Multiple small tasks can run while the developer stays on higher-leverage work – exactly the async promise OpenAI is selling.
Users praise: PR review
Even some critics admit Codex is strong at writing specs and catching issues during pull-request reviews.
Users dislike: speed
A recurring complaint is that Codex can feel slower than Claude Code, even when the final result is solid. Codex-Spark is aimed at this, but it is still in research preview. (For the full head-to-head, see Claude Code or Codex: AI analyzed 10,000 Reddit posts to find a winner.)
Users dislike: UX friction
Setup, approvals, branch iteration, and output formatting still frustrate people who want a smoother inner loop.
Users dislike: limits & platform gaps
Fast limit burn, intermittent quality dips, a weaker native Windows experience, and computer use blocked in EEA/UK/Switzerland at launch all come up repeatedly.
The best line I saw in the discussion called Codex “a near infinite army of juniors” for tiny tasks. That gets at the promise and the fear in one sentence. For experienced operators, it sounds like leverage. For everyone else, it sounds like shrinking entry-level work. The product story and the labor story are now fused.
Real use cases: where Codex looks strongest today
OpenAI’s own material and user reactions point to the same cluster of use cases: backlog cleanup, refactors, codebase understanding, spec-writing, code review, migration work, and PR-bound tasks with clear acceptance criteria. The in-app browser adds a practical web QA loop for non-authenticated pages. Computer use widens the aperture again, especially for GUI-only checks on macOS. The point is not that Codex does everything. It is that more work now fits inside one system than it did a few months ago.
Best current fits
Backlog tickets, utility functions, repetitive refactors, tests, documentation, and code review.
Newly interesting fits
Browser-based verification of local pages, screenshot-guided fixes, and desktop-app checks on macOS.
Still weaker fits
UI-heavy design work, messy exploratory planning, and workflows where speed or conversational steering matters more than rigor.
Case studies and real-world results
Harness engineering
OpenAI says one internal team built and shipped an internal beta product with roughly one million lines of code and zero manually written code, estimating about 1/10th the time versus hand-coding. The useful caveat: they also admit this depended on strong repository structure, strict architectural boundaries, and humans steering the system. OpenAI
Harvey
Harvey’s mobile lead says Codex cut early iteration time by 30–50% – an operational number rather than a magical one, which is what makes it useful for planning. OpenAI
Sierra
Sierra says it can ship in a weekend what previously took a quarter. Punchy, but it is a company quote rather than an independent benchmark. OpenAI
Duolingo and Ramp
Duolingo’s quote focuses on code review quality, saying Codex caught tricky backward-compatibility issues. Ramp says recent Codex releases were a step change and that PR reviews catch bugs the team would have missed. OpenAI
What Codex still does badly
Codex still gets dragged for slowness, branch awkwardness, permission fatigue, brittle setup, and weaker front-end taste than Claude in many real-world workflows. Earlier Hacker News complaints focused on isolated environments and lack of internet access. OpenAI has since added opt-in internet access and a much wider surface area, but the lesson still stands: Codex is strongest when the task is explicit, bounded, and reviewable. Ambiguous design work and tight conversational loops still favor other tools.
The shape of the winner here is becoming clearer. The best tool is not the one with the best vibe. It is the one that fits the work geometry. Codex looks best when you can delegate tightly scoped engineering work and audit the result. Claude still feels better when the work is fuzzy. Cursor still feels better when the editor is the center of gravity. That is a stronger, more useful conclusion than trying to crown one universal winner.
How to think about Codex right now
The easy “Codex kills Cursor” framing is too brittle. A more useful read: Codex is becoming the most interesting workflow-shaped coding product in OpenAI’s stack because it now stretches across async execution, browser verification, PR review, and general digital tasking. That gives it a credible path into developer operations, QA, and even adjacent non-dev work – which is part of the broader pattern I wrote about in 21 Ways AI Agents Are Changing How Work Gets Done in 2026. Codex does not need to beat every competitor at every task to become strategically important. It just needs to become the place where more work happens by default.
Use Codex for
PR review, codebase understanding, async backlog work, browser-verified fixes, ChatGPT-linked access, and teams already standardized on OpenAI.
Use Cursor for
Editor-first development where the IDE itself is the product and you want deep AI assistance inside that environment all day.
Use Claude for
UI/UX-heavy work, exploratory planning, and situations where conversational steering beats rigid execution.
Use Copilot or Windsurf for
Lower-cost entry, GitHub gravity, or a simpler pricing ramp with less emphasis on the broader OpenAI workflow stack.
FAQs about the new OpenAI Codex
Is Codex included in ChatGPT Plus?
Yes. OpenAI says Codex is included with ChatGPT Plus, Pro, Business, and Enterprise/Edu plans, with temporary availability in some lower tiers as rollout and promos continue. help.openai.com
What is actually new in the April 2026 Codex update?
The meaningful additions are the broader workspace model: GPT-5.3-Codex (with a Codex-Spark real-time variant in preview), unified surfaces, IDE extension, rebuilt CLI, in-app browser, computer use on macOS, PR workflow expansion, thread automations, and a new token-based credit billing model from April 2. OpenAI · Changelog
How does Codex pricing actually work now?
Two layers. First, access is bundled into ChatGPT plans ($20 Plus, $100 Pro, $200 Pro, plus Business and Enterprise). Second, usage beyond the bundled limits is billed as credits per million input, cached-input, and output tokens, with cached input discounted roughly 10x and Fast Mode doubling consumption. That means predictable entry cost with API-style overage economics on top. Codex rate card
What is GPT-5.3-Codex-Spark?
A smaller version of GPT-5.3-Codex positioned as the first Codex model tuned for real-time coding, with target throughput above 1,000 tokens per second. It is in research preview for ChatGPT Pro users in the Codex app, CLI, and IDE extension. Expect it to sharpen the inner loop; the heavier model still handles long-horizon tasks. OpenAI
Is Codex better than Cursor?
Not universally. Cursor still has the stronger AI-native editor identity and a cleaner inner-loop experience. Codex is more interesting if you care about async cloud work, ChatGPT distribution, PR review, and cross-surface workflows.
Is Codex better than Claude Code?
Codex often gets praise for discipline and precision. Claude still gets praise for front-end taste, broader conversational planning, and a smoother subjective experience in some workflows. The better tool depends on task shape, not slogans. r/ChatGPTCoding · r/ClaudeCode
Does Codex have internet access?
It can, but OpenAI positions internet access as opt-in and scoped. Earlier complaints about isolation are part of why this matters so much in the update story. OpenAI · Changelog
Can Codex browse authenticated pages?
No. The in-app browser does not support authentication flows, signed-in pages, or your normal browser profile. For those, OpenAI says to use your regular browser. In-app browser
What is computer use in Codex?
On supported macOS setups, computer use lets Codex see and operate graphical apps with permissions. It is useful for GUI-only checks and multi-app workflows. It is not available in the European Economic Area, the United Kingdom, or Switzerland at launch, and it raises obvious trust and security considerations worth reviewing before enabling. Computer use
Who should skip Codex right now?
Solo developers on Windows who never leave their editor, teams that already have a settled Claude Code or Cursor workflow with no async backlog problem, and anyone whose work is dominated by ambiguous UI/UX design tasks. The upside of Codex is highest when there is bounded backlog work waiting to be delegated.
Sources and further reading
- OpenAI: Introducing upgrades to Codex
- OpenAI: Introducing Codex
- OpenAI: Codex product page
- OpenAI Developers: Codex changelog
- OpenAI Developers: Codex pricing
- OpenAI Help: Codex rate card
- OpenAI Help: Using Codex with your ChatGPT plan
- OpenAI Help: ChatGPT Pro plans
- OpenAI Developers: In-app browser
- OpenAI Developers: Computer use
- OpenAI: Harness engineering with Codex
- Cursor pricing
- Windsurf pricing
- GitHub Copilot pricing
- Anthropic pricing
- Hacker News discussion
- Reddit: Is Codex really that impressive?
- Reddit: Tried Codex after all the noise
- OpenAI Community: Codex limits discussion
Last tested and updated on April 17, 2026. Pricing and plan limits can shift – always confirm against the official Codex pricing page before committing a team to a tier.
