OpenAI Codex/GPT-5.5 Emerging as a Real Development Workhorse · history
Version 3
2026-05-22 19:45 UTC · 38 items
What
OpenAI's Codex toolchain — combining a CLI, desktop app, and mobile interface backed by GPT-5.5 at the 'xhigh' compute setting — has expanded across every major platform and is now drawing systematic empirical scrutiny of its capability tiers.
The mobile rollout to iOS and Android, accessible through the ChatGPT app, has been confirmed by mainstream technology press including The Verge, TechCrunch, 9to5Mac, and Android Authority [6][8][10]. Desktop computer use — Codex autonomously opening and controlling applications — has generated broad community attention, with Reddit users describing it as 'INSANE' [11] and official documentation confirming 90+ app plugins [13].
The previously open question of whether GPT-5.5 xHigh in Codex outperforms the standard $200 Pro tier is receiving direct empirical treatment: a published 20-task comparison found the Pro tier lost on 14 of those tasks [16], and community and third-party benchmarkers are now systematically comparing compute tiers [18][17].
Why it matters
Codex has moved from a developer-facing coding assistant into a general-purpose autonomous agent available on every major platform — mobile, desktop, and CLI. The empirical evidence accumulating around GPT-5.5 xHigh's advantage over Pro tier matters because it grounds what had been practitioner intuition in replicable tests, potentially reshaping how users allocate spend across OpenAI's product surface.
Open questions
What specific capabilities does Codex mobile expose — does the xHigh compute tier remain available on iOS and Android, or does the mobile surface operate at a reduced capability profile? [8][10]
The 20-task comparison found Pro tier losing on 14 tasks [16], but methodology and task selection are not described in available metadata — how reproducible is this finding across different task categories, and does Artificial Analysis's model comparison corroborate it? [18]
With 90+ app plugins listed for Codex desktop [13] and computer use described as autonomous app control [12][11], what are the sandboxing and permission boundaries — and how do they compare to other computer-use implementations?
Is Willison's model of intensive end-to-end production use reproducible for practitioners without deep familiarity with the underlying open-source projects being extended? [1][4]
Narrative
OpenAI's Codex toolchain — spanning a CLI, a desktop application, and now a mobile interface — has become one of the most-discussed practical AI development environments of mid-2026. Its core capability rests on GPT-5.5 at the 'xhigh' compute setting, and its trajectory from coding copilot to autonomous cross-platform agent has played out over roughly six weeks.
The practitioner record is most detailed in the work of Simon Willison, maintainer of the open-source Datasette project. Over a three-day window in mid-May, Willison used Codex to diagnose a concurrency-triggered segfault by generating a minimal reproduction Dockerfile [1], prototype a content-security-policy experiment involving sandboxed iframe communication [2], build Datasette's official blog using the desktop app's Markdown transcript export feature [3], and ship a configurable rate-limiting plugin in response to crawler traffic disrupting datasette.io — deploying it to production the same day it was written [4]. Each of these was a complete deliverable, not a scaffold, and each was attributed specifically to GPT-5.5 xhigh. OpenAI's own use of Codex surfaced through the Parameter Golf competition retrospective, where a Codex-based triage bot was deployed to manage a wave of AI-agent-submitted entries that propagated invalid strategies at machine speed — faster than human review could respond — creating a recursive dynamic in which AI tools generated review infrastructure to manage AI-generated content [5].
The toolchain's footprint has since expanded across two axes. First, Codex was deployed to the ChatGPT mobile app on iOS and Android [6], confirmed by The Verge, TechCrunch, 9to5Mac, Android Authority, and Thurrott [7][8][9][10], framing the capability as enabling app development on the go. Second, computer use — Codex autonomously opening, reading, and controlling desktop applications — has crossed from developer awareness into broad community attention: Reddit users have described it as 'INSANE' [11], a desktop control thread emerged on r/OpenAI [12], official documentation confirms 90+ app plugins alongside the computer-use capability [13], and a dedicated YouTube demonstration has been published [14]. A Facebook post attributes a major Codex update enabling direct app control to an April 16 announcement [15], suggesting the capability predates its community discovery by several weeks.
The previously informal question of whether GPT-5.5 xHigh in Codex is meaningfully distinct from GPT-5.5 Pro in standard ChatGPT is now receiving empirical treatment. A published 20-task comparison found the $200 Pro tier lost on 14 of those tasks — implying a material advantage for the xHigh compute level that Codex accesses [16]. A Reddit community thread has independently compared the full compute-tier ladder (low, medium, high, xhigh) [17], and third-party benchmarking site Artificial Analysis has published a head-to-head comparison between GPT-5.5 xhigh and GPT-5.3 Codex xhigh [18]. What had been informally understood practitioner intuition is being grounded in replicable methodology, though task domain and selection criteria remain important variables that the available metadata does not fully describe.
Timeline
- 2026-04-16: OpenAI announces major Codex update enabling the AI agent to directly control desktop applications — the capability community observers would later describe as 'computer use' [15]
- 2026-04-28: CUA project released, enabling autonomous control of macOS applications in the background — an early signal of the desktop-agent direction Codex would later expand into [27]
- 2026-05-12: OpenAI publishes Parameter Golf retrospective describing mass AI agent participation, machine-speed propagation of invalid strategies, and an internal Codex-based triage bot deployed to manage submissions [5]
- 2026-05-12: Datasette 1.0a29 released; Willison credits Codex CLI (GPT-5.5 xhigh) with generating a minimal Dockerfile that reproduced a concurrency-triggered segfault [1]
- 2026-05-13: Willison publishes CSP allow-list proof-of-concept built with GPT-5.5 xhigh in the Codex desktop app [2]
- 2026-05-13: Datasette project launches an official blog built using OpenAI Codex desktop; Willison highlights the Markdown transcript export feature [3]
- 2026-05-14: datasette-ip-rate-limit 0.1a0 released and deployed to production; plugin built by Codex (GPT-5.5 xhigh) in response to crawler traffic on datasette.io [4]
- 2026-05-14: OpenAI deploys Codex to ChatGPT app on iOS and Android in preview; confirmed by The Verge, TechCrunch, 9to5Mac, Android Authority, and Thurrott [6][7][8][9][10]
- 2026-05-16: Community observers note Codex has evolved into a full desktop environment agent; separate discussion surfaces around whether GPT-5.5 xHigh in Codex differs from GPT-5.5 Pro in ChatGPT [22][24]
- 2026-05-17: Community commentary characterizes the week as a crossing point for AI coding tools into practical everyday use; speculation emerges about a potential xHigh-speed hybrid configuration [23][25]
- 2026-05-18: Reddit community describes Codex computer use as 'INSANE'; official documentation confirms 90+ app plugins; desktop control discussion spreads across r/OpenAI and r/codex [19][20][12][11][13]
- 2026-05-19: Grok explicitly positions itself against Codex, citing speed, agentic tool use, and long context as differentiating attributes [26]
- 2026-05-20: Published 20-task comparison of GPT-5.5 variants finds Pro tier losing on 14 tasks; Artificial Analysis publishes GPT-5.5 xhigh vs GPT-5.3 Codex xhigh model comparison; Reddit community independently tests full compute-tier ladder [16][18][17]
Perspectives
Simon Willison
Active, approving practitioner who uses Codex CLI and desktop with GPT-5.5 xhigh as the primary implementation tool for complete deliverables — debugging, security prototyping, infrastructure, and deployed production plugins — not as a supplement but as the lead implementer
Evolution: Consistent and deepening across the thread; each use case is more production-critical than the last, from blog scaffolding to a same-day-deployed rate-limiter
OpenAI
Operationally reliant on Codex internally and actively expanding the toolchain's surface area — to mobile, to computer use, and to a 90+ plugin ecosystem — while remaining candid about the emergent risks AI-agent participation creates in open competitions
Evolution: Expanding: the mobile launch is now a documented mainstream product milestone rather than an internal announcement, and official developer documentation confirms the scale of the computer-use and plugin ecosystem
Community practitioners and observers (Reddit, Twitter)
Broadly enthusiastic — with desktop computer use described as 'INSANE' on Reddit — while simultaneously conducting systematic empirical testing of GPT-5.5 compute tiers that is beginning to ground informal practitioner intuition in replicable methodology
Evolution: More empirically active than before: earlier community items were amplification-style, but newer items include head-to-head compute-tier comparisons, direct 20-task testing of Pro vs xhigh variants, and community benchmarking alongside third-party analysis
Mainstream technology press (The Verge, TechCrunch, 9to5Mac, Android Authority, Thurrott)
Confirmatory and descriptive — reporting the mobile rollout as a significant platform expansion without editorial skepticism; framing Codex mobile as enabling app development on the go
Evolution: New consolidated voice this pass: multiple major outlets independently confirmed the mobile launch, elevating it from a community-level report to mainstream technology news
Grok / xAI
Competitive: positions itself against Codex by name, citing speed, agentic tool use, and long context as differentiating attributes
Evolution: Consistent from prior pass; no new positioning items in this cycle
Tensions
- AI agents in open competitions lower barriers to entry and accelerate experimentation, but enable machine-speed propagation of invalid strategies — requiring AI-assisted review infrastructure that human-paced oversight was not designed to provide, raising unresolved questions about attribution and competitive fairness [5]
- Practitioners (Willison) treat GPT-5.5 xHigh as qualitatively superior and deploy against it in production; a 20-task empirical comparison now suggests xHigh materially outperforms the $200 Pro tier, but OpenAI has not published formal documentation distinguishing these tiers — a tension between emerging empirical evidence and absent official specification [16][18][17][24][4]
- Grok positions speed and agentic capability as its advantages over Codex, while community observers describe Codex's computer-use mode as a step-change and Reddit users call it 'INSANE' — an implicit disagreement about which system leads on the agentic dimension [26][11][19]
Sources
- [1] datasette 1.0a29 — Simon Willison (2026-05-12)
- [2] CSP Allow-list Experiment — Simon Willison (2026-05-13)
- [3] Welcome to the Datasette blog — Simon Willison (2026-05-13)
- [4] datasette-ip-rate-limit 0.1a0 — Simon Willison (2026-05-14)
- [5] What Parameter Golf taught us about AI-assisted research — OpenAI Blog (2026-05-12)
- [6] OpenAI's Codex is now in the ChatGPT mobile app — reactive:openai-codex-enterprise-rollout (2026-05-14)
- [7] OpenAI Releases Codex on Mobile in Preview - Thurrott.com — reactive:codex-practical-dev-tool
- [8] OpenAI brings Codex to ChatGPT for iPhone, iPad, and Android with these features - 9to5Mac — reactive:codex-practical-dev-tool
- [9] OpenAI Codex is coming to mobile so you can build apps on the go - Android Authority — reactive:codex-practical-dev-tool
- [10] OpenAI says Codex is coming to your phone - TechCrunch — reactive:codex-practical-dev-tool
- [11] Codex computer use is INSANE : r/codex — reactive:codex-practical-dev-tool
- [12] Desktop Control for Codex : r/OpenAI - Reddit — reactive:codex-practical-dev-tool
- [13] OpenAI Codex Desktop: Computer Use + 90+ App Plugins — reactive:codex-practical-dev-tool
- [14] Computer use in Codex — reactive:codex-practical-dev-tool
- [15] On April 16, #OpenAI announced a major #Codex update enabling ... — reactive:codex-practical-dev-tool
- [16] I Tested All 3 GPT-5.5 Variants on 20 Real Tasks — The $200 Pro Tier Lost on 14 of Them — reactive:codex-practical-dev-tool
- [17] r/codex on Reddit: GPT-5.5 low vs medium vs high vs xhigh — reactive:codex-practical-dev-tool
- [18] GPT-5.5 (xhigh) vs GPT-5.3 Codex (xhigh): Model Comparison — reactive:codex-practical-dev-tool
- [19] OpenAI Codex just evolved from a coding assistant into a full desktop environment agent. It can now open, read, and cont... — reactive:codex-practical-dev-tool (2026-05-18)
- [20] OpenAI Codex is expanding beyond the desktop. If your coding assistant only works in one environment, it's not really an... — reactive:codex-practical-dev-tool (2026-05-18)
- [21] Features – Codex app - OpenAI Developers — reactive:codex-practical-dev-tool
- [22] @kimmonismus This is quietly much bigger than “Codex got new settings”. — reactive:codex-practical-dev-tool (2026-05-16)
- [23] @thsottiaux @kr0der If OpenAI launches a GPT 5.5 xHigh with the speed of GPT 5.3 Codex Spark and it really works at the ... — reactive:codex-practical-dev-tool (2026-05-17)
- [24] @aniketapanjwani So wait a second... Chat gpt 5.5 in xHigh intelligence within codex IS different to Chat Gpt 5.5 Pro wi... — reactive:codex-practical-dev-tool (2026-05-16)
- [25] This week, two major AI coding tools crossed into practical, everyday use. No hype — just deployed features you can test... — reactive:codex-practical-dev-tool (2026-05-17)
- [26] @0thernes_ai @electrolyse4 @grok_sr @teslaownersSV @claudeai @codex Thanks! Speed, agentic tool use, long context, and s... — reactive:codex-practical-dev-tool (2026-05-19)
- [27] Show HN: Drive any macOS app in the background without stealing the cursor — reactive:agentic-coding-safety (2026-04-28)