A Reddit post with 307 upvotes told coding-agent users their usage quota was being silently drained by a hidden feature. The same comment section spent the next six hours taking the claim apart, piece by piece, without fully resolving it either way. That's the more useful story: not "OpenAI is secretly burning your tokens," and not "nothing happened here" — something real shipped on a specific date, and the viral framing outran what the evidence in the thread actually supports.
TL;DR
| Claim | What the thread actually shows |
|---|---|
| "OpenAI silently turned on auto-review for everyone on Aug 7" | OpenAI's docs say auto-review is off by default and opt-in via config. A real, narrower change — "safer auto-review defaults for cyber-capable models" — shipped Aug 5 in v0.146.1, which could explain some unexpected activations without matching the "for everyone" framing |
| "It burns 100,000 tokens to output 100" | Unverified — this figure comes from the OP's own log reading, not from the usage chart shown, and wasn't independently reproduced in the thread |
| "10.4 million tokens in a week" | The chart cited actually counts turns (reviewer calls), not tokens — several commenters flagged this directly |
| "The reviewer secretly reads your entire conversation" | OpenAI's docs describe a "compact transcript plus the exact approval request," explicitly excluding hidden reasoning — narrower than "your entire conversation from the beginning" |
| How expensive is a turn, really? | One commenter reported the reviewer runs on a comparatively cheap model (~$0.20/million tokens) — cutting against the "quota-devouring" framing, though not fully settling it |
| How to check/fix it | Check chatgpt.com/codex/cloud/settings/analytics#usage; disable "approve for me" and/or explicit auto-review settings if you want it off |
The claim, as originally posted
The r/codex post from u/Stunning-Angle-9239 laid out a specific, falsifiable-sounding claim: on August 7, 2026, Codex CLI v0.147.0 shipped with a feature called codex-auto-review that, according to the post, silently sends a copy of the entire conversation to a second AI model every time the agent wants to run a command or edit a file — without the user turning it on. The poster's own numbers: 141 auto-review runs in one week, ~10.4 million tokens consumed, a worst day of 46 checks in 19 minutes accounting for 28% of that day's usage, and single checks costing up to ~195,000 tokens.
The post pointed to two pieces of real evidence: the v0.147.0 release notes and PR #36373 on the openai/codex GitHub repo. Those are genuine, checkable artifacts — the disagreement in the thread isn't about whether a change shipped, it's about what that change actually does and costs.
What OpenAI's own documentation says
OpenAI's sandboxing/auto-review docs describe a narrower mechanism than the post's framing. Auto-review replaces manual human approval only at sandbox boundaries — elevated-permission shell commands, blocked network requests, edits outside allowed directories, MCP or tool calls that need approval — and only engages with interactive approval policies in the first place. The reviewer receives, in OpenAI's own words, "a compact transcript plus the exact approval request," not a fresh re-read of the entire conversation from message one. Hidden reasoning and chain-of-thought are explicitly excluded. And critically: the docs describe it as requiring the config setting approvals_reviewer = "auto_review" — not on by default.
That directly contradicts the strongest version of the claim ("nobody turned this on, it just switched itself on"). It does not, on its own, resolve the thread, because commenters reported genuinely inconsistent experiences.
The change that plausibly explains the confusion
Independent of the Reddit thread, Codex's own changelog shows something did ship right around the dates in question: v0.146.1, released August 5, 2026, applied "safer automatic-review defaults for cyber-capable models." That's a real, specific, and much narrower change than "silently enabled for everyone" — it reads as a safety-motivated default shift tied to specific model capability classes, not a blanket flip of a setting for the whole user base. If a user's account or session touched a model Codex classifies as "cyber-capable," this could plausibly cause auto-review to activate under conditions the user never manually configured, which would explain why some Reddit commenters swore they never enabled it while others reported zero impact and confirmed it stayed off. Two days later, v0.147.0 added a --approve-for-me flag — a related but separate mechanism for automated approvals that several commenters conflated with auto-review itself.
The technical rebuttals, and how strong they actually are
Several commenters made the same core correction independently, which is worth taking seriously: the usage chart in question breaks down turns by model, not tokens. A turn is one call to the reviewer; it says nothing on its own about how many tokens that call consumed. u/Dekeiy's three-word reply — "turns != tokens" — got more upvotes-in-spirit from the rest of the thread than almost anything else posted. u/Copenhagen79 went further, stating flatly that the 10.4 million figure conflated Luna-model requests with tokens and that "10.4 million Luna-tokens in a week is nothing."
The pricing detail matters here. u/Professional-Yam2565 reported checking and finding the reviewer runs on a model referred to in the thread as "Luna" (OpenAI's gpt-5.6 family), priced around $0.20 per million tokens — cheap relative to frontier reasoning models, and per that commenter, recently cut further (they cited "10 to 12 times cheaper" than an earlier price). If that number is accurate, even a genuinely high turn count translates to a modest dollar cost, which undercuts the "ate your entire quota" framing without fully resolving whether quota accounting inside a fixed subscription plan tracks dollar cost one-to-one.
Not every technical rebuttal landed clean, though — u/Im_Working_Right_Now asked directly for evidence that the reviewer reads the entire codebase/conversation rather than the compact transcript OpenAI's docs describe, and no one in the visible thread produced that evidence. That's the single biggest unresolved gap between the original post's strongest claim and what's actually been shown.
What real users reported seeing
The thread wasn't uniformly skeptical. u/JustMy2Centences reported a week where codex-auto-review ran 224 times against 100 combined Sol/Terra/Luna turns — a genuinely lopsided ratio, even accounting for the turns-not-tokens correction. u/Responsible-Bill-223 said auto-review was "eating almost half my budget during some time periods." u/Frosty_Rub_1382 reported it accounting for "like 90%" of their usage after checking their own logs. Against that, u/Emergency-Bobcat6485 reported having auto-review disabled the entire period with zero activation, and u/nps44 said it stayed disabled for them with no measurable difference. u/Nearby-Attempt9812 offered a plausible dividing line: users who never used --approve-for-me and instead ran with sandbox_mode = "danger-full-access" and approval_policy = "never" (skipping the review step entirely, a different risk tradeoff) reported never seeing the spike — consistent with auto-review's actual trigger condition being approval-policy-dependent, as OpenAI's docs describe.
The honest bottom line
This is not a clean "hoax" or a clean "confirmed bug." What's independently verifiable: a real configuration change (v0.146.1's "safer defaults for cyber-capable models") shipped August 5, 2026, two days before the date the original poster flagged. What's contested and not independently verified: the specific 10.4-million-token figure, the "100,000 tokens to output 100" ratio, and the claim that the reviewer reads an entire conversation from scratch rather than the compact transcript OpenAI's docs describe. What's a fair correction regardless of which side is right: the usage chart being screenshotted across the thread counts turns, not tokens, and conflating the two overstates the claim's precision even if the underlying concern — auto-review activating without a clear opt-in — turns out to be legitimate.
If you're worried about your own usage, the actionable steps in the thread are concrete regardless of how the token-count dispute resolves: check chatgpt.com/codex/cloud/settings/analytics#usage for your own turn breakdown by model, and if you see codex-auto-review running far more than expected, disable "approve for me" in Codex's app permissions and/or explicitly turn off approvals_reviewer = "auto_review" in your config rather than assuming a specific dollar figure without checking.
The broader lesson generalizes past this one thread: usage dashboards that break activity down "by model" without a corresponding token or dollar axis invite exactly this kind of misread, and any coding-agent vendor shipping an automated approval or review layer should expect users to scrutinize its cost model the moment a chart looks alarming, whether or not the alarm turns out to be justified.
Related on explainx.ai
- OpenAI's 80% usage reset and the $200 Pro plan
- Enable the 1M token context window in Codex CLI with GPT-5.6 Sol
- Cursor restores its dollar-cost usage page for token transparency
- The GPT-5.5 Codex reasoning-token clustering bug
- Claude, Codex, Cursor usage limits — how the resets actually work
- Destructive Command Guard — a safer alternative to full auto-approve
- Codex vs. Claude Code: the full agent comparison
Primary sources: r/codex thread (u/Stunning-Angle-9239) · OpenAI Codex auto-review docs · Codex v0.147.0 release notes · PR #36373
This is a fact-check of a contested community claim, not a confirmed technical audit — several specific figures (10.4 million tokens, the exact reviewer model and price) come from individual Reddit users' self-reported log analysis and were not independently reproduced by explainx.ai. Verify against your own usage dashboard before drawing conclusions about your own account. Follow @explainx_ai for updates if OpenAI issues an official statement.