OpenAI Codex’s reported 90M-install week was an npm spike, not 90M users
OpenAI Codex’s May 2026 reported 90M installs in one week are best read as a package download spike around @openai/codex, not 90M active developers; npm counts can include automation, CI and re fetches. The spike likely combined real demand with noisy measurement: GPT 5.5 API access, earlier GPT 5.3 Codex momentum,...
Published byEdited with GPT-5.5Images generated with GPT Image 2
OpenAI Codex’s May 2026 reported 90M installs in one week are best read as a package download spike around @openai/codex, not 90M active developers; npm counts can include automation, CI and re fetches.
The spike likely combined real demand with noisy measurement: GPT 5.5 API access, earlier GPT 5.3 Codex momentum, one line CLI installs and the Codex SDK all made Codex easier to test and automate.
Use the number as a signal of developer attention, not proof of retention, productivity gains or manual installs by 90M people.
Create a landscape editorial hero image for this Studio Global article: OpenAI Codex’s Reported 90M-Install Spike, Explained. Article summary: The reported 90M installs are best read as weekly npm download/install activity for Codex CLI, not 90M active developers; separate npm snapshots showed even larger counts while warning they do not equal real usage.. Topic tags: ai, openai, codex, coding agents, developer tools. Reference image context from search candidates: Reference image 1: visual subject "The outlet attributes the surge to the rollout of GPT-5.5, which it says expanded Codex's context capabilities to a **400K token** window for the tool and API support up to **1,000" source context "OpenAI Codex reaches 90M installs in one week | Let's Data Science" Reference image 2: visual subject "# OpenAI Codex Statistics 2026: Key Numbers, Data & Facts. Current OpenAI Codex CLI statistics
openai.com
OpenAI Codex’s reported 90 million installs in a week is a useful signal, but it is easy to overstate. The best reading is that the Codex CLI package saw exceptional download/install activity while developers were testing newer OpenAI coding models and workflow integrations. It is not evidence that 90 million people became active Codex users .
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
What is the short answer to "OpenAI Codex’s reported 90M-install week was an npm spike, not 90M users"?
OpenAI Codex’s May 2026 reported 90M installs in one week are best read as a package download spike around @openai/codex, not 90M active developers; npm counts can include automation, CI and re fetches.
What are the key points to validate first?
OpenAI Codex’s May 2026 reported 90M installs in one week are best read as a package download spike around @openai/codex, not 90M active developers; npm counts can include automation, CI and re fetches. The spike likely combined real demand with noisy measurement: GPT 5.5 API access, earlier GPT 5.3 Codex momentum, one line CLI installs and the Codex SDK all made Codex easier to test and automate.
What should I do next in practice?
Use the number as a signal of developer attention, not proof of retention, productivity gains or manual installs by 90M people.
The headline number was reported as a weekly download/install figure, not a lifetime installed base or active-user total . That distinction matters because Codex CLI is distributed as the @openai/codex package on npm, where the official package page tells developers to install it with npm install -g @openai/codex, alongside Homebrew and downloadable binaries .
npm download counts are a high-noise proxy. A separate npm-focused analysis said the official npm page showed 195,488,301 weekly downloads for @openai/codex and warned that npm downloads can include automated installs, CI, short tests, re-fetches and distribution effects . OpenAI’s own GitHub materials include a GitHub Actions workflow that installs Codex before running an automated changelog task, showing how repeatable automation can create package downloads without mapping one-to-one to new human users .
What likely drove the spike
1. GPT-5.5 gave developers a reason to retest Codex
OpenAI said GPT-5.5 and GPT-5.5 Pro became available in the API in an April 24, 2026 update . The same announcement said GPT-5.5 excels at writing and debugging code, can carry more of the work itself and uses significantly fewer tokens to complete the same Codex tasks .
That makes GPT-5.5 a credible catalyst for renewed Codex experimentation. Developers had a fresh reason to reinstall, update, benchmark or wire Codex into local and automated workflows. The available sources do not quantify how much of the reported 90M spike came from GPT-5.5, so it should be treated as a major likely contributor rather than the sole proven cause.
2. Codex CLI and the SDK are built for easy distribution
Codex is not just a web assistant. OpenAI describes it as a coding partner for tasks such as pull requests, feature work, complex refactors and migrations, powered by its frontier coding models . The CLI lowers the adoption barrier further because developers can install it globally with a one-line npm command and run it from the terminal .
OpenAI’s general-availability post also emphasized the Codex SDK, which lets teams embed the same agent that powers Codex CLI into their own workflows, tools and apps . That is strong product distribution, but it also means installs can be triggered by scripts, CI jobs and repeated setup processes rather than one-time manual downloads .
3. Codex already had momentum before the headline
The npm surge did not appear in isolation. Fortune reported in March 2026 that, since early February, more than 1 million people had downloaded the Codex desktop app and Codex had more than 1.6 million active weekly users, according to OpenAI . Moneycontrol separately reported that the standalone Codex app crossed 1 million downloads in its first week on Mac and that usage rose 60% week over week after the February 2 launch and GPT-5.3-Codex rollout .
OpenAI’s February 5, 2026 GPT-5.3-Codex announcement described that model as its most capable agentic coding model to date and said it was 25% faster than the previous version . Those earlier milestones point to real adoption momentum before the later package-download spike, even though they are separate from the 90M npm-style metric.
4. AI coding-agent competition made npm a scoreboard
The Codex surge also fits the broader race among coding agents. An npm API snapshot collected on May 6, 2026 reported about 210.5 million last-month downloads for @openai/codex versus about 46.5 million for @anthropic-ai/claude-code, putting Codex roughly 4.5x ahead on that package-download window .
That comparison is useful as a developer-attention signal, but it has the same caveat as the 90M headline. npm downloads can show which tools are being pulled into environments at scale; they do not prove retention, productivity gains or the number of active human users .
How to read the metric without getting fooled
Signal
Reasonable takeaway
Bad takeaway
Reported 90M installs in one week
A major burst of weekly download/install activity
90M active Codex users
Official npm install path for @openai/codex
Low-friction CLI distribution through developer tooling
Every download was a manual install
195,488,301 weekly npm downloads observed by a separate analysis
Extreme package-level attention, with automation mixed in
A clean user-count metric
1.6M weekly active users reported by Fortune, citing OpenAI
Separate evidence that Codex had real usage momentum
Proof that npm downloads equal active users
Bottom line
OpenAI Codex’s reported 90M-install week is best understood as a distribution shock: GPT-5.5, GPT-5.3-Codex, the Codex SDK, one-line CLI installation and competitive attention all gave developers and automated systems reasons to pull the package .
The caveat is just as important as the spike. npm-style download activity is not the same as active usage. The safer conclusion is that Codex became highly visible in developer package infrastructure, not that 90 million developers actively used it in a week .
