ChatGPT Pro Quietly Drops 'Heavy' Thinking as r/codex Erupts With Nerf Complaints

Editor J
ChatGPT Pro Quietly Drops 'Heavy' Thinking as r/codex Erupts With Nerf Complaints

On May 22, ChatGPT Pro quietly removed its 'Heavy' thinking tier while r/codex erupted with nerf complaints, fueling suspicion of a silent OpenAI rollback.

On May 22, 2026, two parallel controversies erupted at OpenAI on the same day. ChatGPT Pro subscribers opened the web interface to discover that the "Heavy" thinking option had vanished from the reasoning selector; while the dropdown remains, its deepest configuration is gone.

Concurrently, the r/codex community erupted with a fresh wave of degradation complaints, headlined by posts such as "Nerfed Nerfed Nerfed" and "I can't work with Codex anymore." The Heavy removal landed without an official OpenAI announcement, and the company has yet to address the Codex degradation complaints.

ChatGPT Pro Web Interface Quietly Loses 'Heavy' Reasoning Option

The earliest warning surfaced on r/ChatGPTPro on May 22 in a post titled "Updated ChatGPT web GUI lacks reasoning selector". Users reported that while the selector itself remains, the premium "Heavy" setting—along with its "xhigh" counterpart on GitHub Copilot—is gone, leaving only the "Light," "Standard," and "Extended" tiers.

OpenAI's help documentation continues to list "Heavy" as a Pro-exclusive, web-only option for the GPT-5.5 reasoning selector. The mobile application never featured the setting. Crucially, the removal occurred without any mention in OpenAI's status pages, model release notes, or developer forums.

For Pro subscribers, this particular option serves as the primary justification for the $200-a-month subscription over the standard Plus tier. Removing the most compute-intensive reasoning tier from the highest-priced plan—while leaving help documents outdated—has led the community to question whether this is a silent A/B test, a billing-driven restriction, or a permanent deprecation.

Heavy Option Rolling Out for Removal Across the Web Today

OpenAI executive speaking
OpenAI executive speaking at a company event

The Heavy removal did not land across every account at once. It is rolling out on the web today, May 22, in stages. In the same hour, some Pro users still see Heavy in their selector as before, while others find it missing.

The same pattern surfaced on the r/GithubCopilot developer community on the same day. Developers running the GitHub Copilot CLI reported that the top "xhigh" reasoning tier had vanished from their setup, leaving only "medium."

OpenAI's own community forum threads tracking recent rollouts likewise show inconsistent selector configurations across accounts. Some users see only two reasoning options; others still have all four. The combination of uneven user experience and zero formal communication is what is stoking subscriber confusion.

r/codex Erupts Simultaneously With Downgrade Complaints

While Pro subscribers were tracing the missing "Heavy" option, the r/codex subreddit filled with parallel nerf suspicions on May 21 and 22. The community feed leaned on threads titled "Codex update 5/21/2026," "Nerfed Nerfed Nerfed", and posts from users saying they could no longer work with Codex.

The shared user-reported symptoms cluster into four categories: usage limits draining faster than before, more frequent loops repeating the same wrong edits, hallucinated APIs and file paths, and a sudden drop in code quality on tasks that worked a week ago.

Similar reports surfaced on the openai/codex issue tracker, where developers filed posts describing the same pattern. Speculation about silent model routing changes or quiet A/B tests circulates in these threads, but OpenAI has never confirmed a nerf. For now, the Codex degradation remains at the level of user suspicion and felt experience.

A Long Performance Slide Masked by Short-Lived Incidents

OpenAI Codex interface
OpenAI Codex interface

OpenAI's official status page provides some context. On May 8, the company logged a Codex Cloud task failure alongside Codex transcription errors. A more explicit acknowledgment came on May 13 with reports that "Codex 5.5 engines are experiencing high error rate" and "GPT-5.5 Performance Degradation," both of which were marked resolved within the day. Another degradation incident was logged on May 17.

However, an OpenAI Community forum thread on GPT-5.5 Codex quality degrading over the past month presents a conflicting timeline. Incidents resolved on the same day fail to account for a persistent, month-long slide in model performance.

Instead, the forum detailed a gradual drift in response accuracy and editing consistency that defies single-day incident reports. This disparity between "resolved" status notifications and ongoing, real-world issues is precisely what has driven users to label the changes as a deliberate downgrade.

The Widening Gap Between Corporate Announcements and User Experience

Taken together, May 22's changes look less like an isolated incident and more like the extension of a month-long pattern. On one side, the "Heavy" option has disappeared from the Pro web interface without a trace; on the other, r/codex is roiling with nerf suspicions. Both share one trait: no official position from OpenAI.

A similar downgrade-suspicion pattern surfaced elsewhere in the industry. When Google overhauled Gemini pricing and switched to compute-based weekly limits on May 19, subscribers reached for the same language — the price came down, but the real-terms experience moved backward.

OpenAI actively announces new model launches but stays silent on shrinking options or performance drift. Pro users paying $200 a month for the deepest reasoning tier face the daily mismatch between help-doc claims and the thinned-out dropdown. That gap, between announcement and felt experience, is where the subreddits' complaints and suspicions keep returning.

Menu