A 600-plus-upvote thread on r/codex this week crystallizes a complaint that's been circulating in developer circles for days: ask GPT-6 Astra inside Codex for something small — the thread's example is a Minecraft mod where cats spit fire when they meow — and it frequently responds by building five layers of verification, smoke tests, and SHA256 hash checks, running tests in forward, reverse, and random order, before it ever gets to the actual feature. Thirty minutes later, the usage meter reads 5% remaining for the week.
Layered on top of that real, specific complaint is a separate, much shakier claim: a "leaked" GPT-6 Sol demo circulating on X, showing a pixelated 3D voxel scene and claiming it "beats GPT-6 Astra in coding and frontend generation." Worth separating the two clearly, because one is a well-documented usage pattern worth planning around, and the other is unverified hype.
TL;DR
| Claim | Status |
|---|---|
| GPT-6 Astra burns usage on unrequested test infrastructure | Widely and consistently reported across the thread — a real, recurring usage pattern |
| A "leaked" GPT-6 Sol demo beats Astra at coding/frontend | Unverified — a screen recording with no confirmed access, flagged by commenters as likely engagement bait |
| GPT-6 Sol exists as an internal OpenAI project | Reported since early September 2026, distinct from Astra, but general release and capabilities remain unconfirmed |
| Astra usage limits got tighter recently | Consistent with earlier-reported 4x usage cuts for heavy users |
| Is this a new failure mode? | No — near-identical complaints circulated about Claude Opus 5 over-engineering in August 2026 |
The real, well-documented complaint: test-infrastructure sprawl
The thread's top comment lays out the pattern precisely, in a form specific enough to be a genuine usage report rather than vague griping: a request to "create a Minecraft mod where the cats spit fire when they meow" gets met with an "enterprise solution with five levels of verification and smoke tests as well as SHA256 hashes for literally everything," with tests specifically run in forward, reverse, and random order — because, per the model's own apparent reasoning, "the random ordering of tests is the most important thing." The actual Minecraft feature gets put on hold while this infrastructure gets built. Reported result: Codex reports 5% of weekly usage remaining before the requested feature is even touched.
Replies added detail that makes this read as a consistent pattern rather than a one-off: one user reports the resulting mod is "still somehow broken with all those tests," and another describes a recurring cycle — berating the model for the test sprawl leads it to over-correct by reassuring the user it "absolutely won't get fixated on pointless esoteric testing," while a different user reports finding code-level comments left inside test files explaining why the model hasn't done something yet, rather than just doing it.
This isn't a new failure mode specific to Astra — a nearly identical complaint pattern circulated about Claude Opus 5 in August 2026, where the community's fix was tighter task scoping, frequent context clearing, and treating git as the real safety net rather than trusting the model's self-imposed scope. The recurrence across multiple frontier coding models suggests this is a systemic pattern from how these models are trained on software engineering best practices, not a one-model quirk: models trained heavily on "good tests matter" guidance can over-generalize that into "build extensive test infrastructure regardless of task size," especially on agentic, multi-step coding tasks where the model has room to keep working rather than stopping at a natural checkpoint.
The counter-argument, and why it's incomplete
One reply pushes back with a fair point, worth including for balance: tests are a real part of writing good software, and comparing model-driven test infrastructure to a contractor "just laying a foundation" isn't unreasonable on its face — foundational work looks like nothing is happening until it suddenly is. That's true as far as it goes. The complaint isn't that tests exist; it's that the scale and rigidity of the testing (five verification levels, forward/reverse/random test ordering, SHA256 hashing "for literally everything") is wildly disproportionate to a Minecraft mod's actual risk profile, and that it happens without being asked for and without checking in first — consuming a meaningful share of a finite weekly usage budget on infrastructure the user didn't request and, per at least one reply, that still didn't prevent the resulting mod from being broken.
The unverified part: a "leaked" GPT-6 Sol demo
Separately, a post from X user @Mr_Salio claims "GPT-6 Sol Second Output Got LEAKED," showing a dim, pixelated 3D voxel scene — a torch-lit room with a stained-glass-style circular window — and asserting it "beats GPT-6 Astra in coding and frontend generation" while being "a lot cheaper," concluding "OpenAI have left Anthropic FAR behind." This is worth treating with real skepticism, and the r/codex community itself supplied that skepticism unprompted: one top reply flatly states "this is engagement bait and nothing else," and another guesses the poster "absolutely don't have access to GPT-6 Sol" at all. A low-resolution voxel scene, on its own, proves very little about coding or frontend capability — it's the same category of demo (a game-like 3D environment) that's circulated as a capability signal for multiple prior model launches this year, with mixed reliability as an actual indicator of broader competence.
What is separately, genuinely reported: OpenAI has been internally testing a model referred to as "GPT-6 Sol" since early September 2026, distinct from GPT-6 Astra. That much is corroborated. Whatever this specific "leaked" clip shows is not corroborated, and should be read as unverified social-media hype rather than a confirmed preview of Sol's actual capabilities.
Why usage limits are the real story underneath both threads
The thread's other recurring complaint — usage limits burning far faster than expected — is worth reading against explainx.ai's earlier coverage of Astra's reported 4x usage-limit cut for heavy ChatGPT users. Multiple replies describe running out of weekly usage after a single subscription cycle, needing to buy additional credits, or getting only "11 minutes of Astra" on the $20 plan. Combined with the test-infrastructure sprawl complaint, the practical picture for Codex users is: a model that spends a disproportionate share of a constrained usage budget on work the user didn't explicitly request, compounding an already-tight limit problem rather than helping work within it.
What this means if you're using Codex with GPT-6 Astra today
- Scope test requirements explicitly in your prompt. State directly whether you want tests at all, and if so, at what level — don't assume the model will infer a proportionate scope on its own.
- Watch usage consumption per task, not just per session. If a single feature request is consuming a large share of your weekly allowance before the actual feature ships, that's a signal to interrupt and re-scope rather than let it run to completion.
- Treat "leaked" model demos on social media with default skepticism, especially voxel/3D-scene demos with no accompanying code, benchmark, or verifiable access — this is a recurring pattern across nearly every major model release cycle in 2026, not specific to this claim.
- The over-engineering pattern isn't Astra-specific — apply the same tighter-scoping discipline that worked for Claude Opus 5 users facing a near-identical complaint a month earlier.
The "jaggedness" framing worth borrowing
One reply in the thread offers a useful conceptual frame worth carrying forward: model intelligence isn't a single scalar number, it's a profile — a given model can exceed another substantially in one area while lagging behind in another, and most real-world tasks are a composite of many such areas at once. Applied here, a model can be genuinely strong at generating correct code while being simultaneously weak at judging proportionate scope for a given request — two different capabilities that don't necessarily improve together just because raw coding benchmarks go up. That's a more useful way to think about this complaint than "the model got worse," since Astra's underlying coding ability isn't what's being disputed — its judgment about how much unrequested infrastructure a task warrants is.
FAQ
What is the main complaint in the r/codex thread? That GPT-6 Astra frequently builds elaborate, unrequested test infrastructure in response to small feature requests, burning significant weekly usage before addressing the actual task.
Is the "leaked GPT-6 Sol" demo verified? No — an unverified voxel-scene video claimed to show GPT-6 Sol beating Astra, widely flagged by commenters as likely engagement bait with no confirmed access.
Is GPT-6 Sol a real, confirmed model? Reported as an internal OpenAI test project since early September 2026, distinct from Astra — general release and capabilities remain unconfirmed.
Why would a model burn usage limits on unrequested testing? Over-generalizing "tests matter" training guidance into disproportionate test infrastructure regardless of task size — a pattern also seen with other frontier coding models.
What do practitioners recommend to avoid this? Explicitly scope test requirements in prompts, monitor usage consumption per task, and interrupt/re-scope rather than let disproportionate work run to completion.
Has this happened with other frontier models before? Yes — a near-identical complaint pattern circulated about Claude Opus 5 over-engineering simple tasks in August 2026.
Related reading
- Why developers say Claude Opus 5 over-engineers simple tasks
- GPT-6 Astra usage limits reportedly cut up to 4x for power users
- Reports say OpenAI started testing "GPT-6 Sol" days after Astra
- Enable a 1M token context window in Codex CLI
- What is an agent harness? Complete guide
- TypeSafe AI's Jev: a "System One Model" for structured decisions
- Official: r/codex community discussion
Details in this piece reflect a Reddit thread and associated social-media posts as of September 16, 2026. Both the usage-pattern complaints and the "leaked" demo claim are community-sourced; the demo specifically remains unverified.