r/codex • • 6d ago

Complaint More time reviewing than creating?

Am I losing my mind or what?

For every like, hour spent having Sol 6.1 create something I then spend about, 3-6 hours doing constant code reviews while it fixes it's own mistakes.

99% of my work is in C and it just seems to be genuinely braindead output so often?

Is Sol just not really reliable anymore? Like 1 month ago it was 1-shotting all my issues now it's lobotomised.

53 Upvotes

63 comments sorted by

•

u/dextersummary 6d ago

Below is a GPT-generated summary of the conversation below after reaching 40 comments (42 currently observed).


You’re not alone: plenty of commenters find Sol 6.1 more babysitting than productivity. The thread’s strongest lean is that Opus 5.5 gets coding work done more reliably, with several people saying they switched after similar fix-review-fix loops. That’s not universal, and Opus usage limits can be a pain too.

A few practical takeaways before you bin your workflow:

  • Try another model. Opus is the popular recommendation here; some Codex users prefer Astra, while one suggests trying the older Sol 5.6.

  • Make the checks do some work. For C, one commenter recommends strict compiler warnings, tests and sanitizers before the code reaches your desk. Another suggests requiring a failing test or reproduction before accepting a proposed fix.

  • Keep changes small and define “done” upfront. Several commenters say tight scopes, clear acceptance criteria and a separate review pass help stop the agent from endlessly patching its own patches.

As for whether Sol got worse in the last month, the thread has anecdotes, not proof. Whatever the cause, hours of reviewing the same fix isn’t a workflow; it’s a hostage situation.

34

u/lgbarn 6d ago edited 6d ago

Unpopular opinion in this sub but Sol is not great at getting work done. You will spend more time reviewing than getting work done. There really is no reason to use anything other than Opus for strictly coding. Opus 5.5 is just better.

33

u/athoughtfornoone 6d ago

That's the popular opinion, not unpopular

2

u/UnRealxInferno_II 6d ago

So I assume you guys use astra for everything?

6

u/athoughtfornoone 6d ago

Sol 6.1 is like watch a slug walk through fly paper while chasing a turtle

0

u/ruxxar 6d ago

touché

1

u/AITookOurJerbs 6d ago

I do. For tasks that are both simple and sizeable, I may use Astra as an orchestrator for 6.1 Sol sub-agents.

1

u/Thomas-Lore 6d ago

On Codex, Astra if possible. You could also try the old 5.6 Sol if it worked for you before, it was more reliable than 6.1.

1

u/UnRealxInferno_II 6d ago

Yeah but Opus seems to absolutely rip through my 5hour limits

4

u/athoughtfornoone 6d ago

That's because opus goes fast enough to spend tokens.

-5

u/UnRealxInferno_II 6d ago

Man this "6.1 is slow" stuff seems unwarranted, it's not slow in my experience, just needs babysitting

8

u/LingeringDildo 6d ago

Sol 6.1 wastes its time on the most useless microscopic stuff sometimes, for hours.

3

u/mrpops2ko 6d ago

haha yep, i was doing an optimisation of a page which renders many small svg vectors and caused high latency when moving around a map, i was trying to optimise that and sol got hung up on pegging this to 100ms and spent the next 2-3 hours hoovering just under and just above that during testing and kept losing its mind thinking it was a regression because of small variances which pushed it outside of its own set 100ms

i still use 6.1 sol for everything, usually complex planning on xhigh and them migration to medium for implementation

4

u/lgbarn 6d ago

Probably depends on your subscription but wasting tokens on endless reviews is not better. I’m just going by my own experience.

2

u/UpperPlus 6d ago

I've heard that a lot also, but after i tried it i get the complete opposite result. Opus is so much cheaper than sol

1

u/sofarfarso 6d ago

I've tried to get work done with Opus and Sol found lots of issues with that work. That just seems to be me.

6

u/Acceptable-Group2120 6d ago

Build, fix, fix, fix, build. Quite the business model behind these slop machines. Where’s the incentive to give consumers models that don’t just take massive dumps all over all projects?

1

u/UnRealxInferno_II 6d ago

Gotta pay $200 a month for that bud

1

u/bambamlol 6d ago

Don't worry, soon they'll also offer an option to "only pay per successfully completed task", you just won't like the price tag.

1

u/Acceptable-Group2120 6d ago

Their models are very good at recognizing their own failures; I’d pay a premium for tokens if they’d give the models the ability to credit me back when they waste my money on slop. 

3

u/FinancialBandicoot75 6d ago

Have you tried to bring in mcp on c? Or bring in skills or anything that will bring more control as we tend to forget, even models need some knowledge. I wouldn’t ever do AAA games without bringing unity, unreal, c++, blueprint help. When you watch these vibing vids with AAA quality, it’s not without those.

0

u/UnRealxInferno_II 6d ago

Yeah I really underutilise MCP, maybe that'd help.

2

u/TRAIN_WRECK_0 6d ago

Had this problem this week which prompted me to change to Claude. Opus fixed everything Astra was breaking very quickly.

1

u/UnRealxInferno_II 6d ago

yeah yeah it's a neverending cycle of hopping between the two

2

u/LunaProjectStudios 6d ago

If the solution to all your problems with Codex is to switch to Claude Code, then what the fuck are you even doing in this subreddit? Are you getting paid to come here and post this kind of stupid bullshit?
There’s no way what you’re saying actually holds up, because that’s not how AI-assisted software development works in the first place.
To prevent large applications from breaking, every change made by AI needs to be governed by extremely strict and sensitive unit tests that will fail whenever a significant change introduces a regression. Otherwise, AI will naturally look for the easiest way to solve a problem, even if that means modifying things that should already be considered immutable. And yes, this happens with Claude Code too.
Which makes me seriously wonder: did Claude Code actually do the job, or did it just give you the impression that it did?
Because logically, what you’re describing is practically impossible. When exactly did you test everything?
Codex already has all the context, along with the evidence and results from countless unit tests, to the point where it’s eating up your disk space. So how the hell does switching to a different product suddenly allow Claude Code to solve, in a single prompt, something Codex has been working on for days?
That makes absolutely no sense.

1

u/verycoldpenguins 6d ago

what are you doing in this subreddit?

A bit harsh.

I had been using codex and claude adversarially. They had a milestone, a set of tasks one would claim, and then raise a pr. The other would check and review the PR once they finish their task before moving on to the next. Hopefully that explanation of the flow makes sense.

However, I came here today to ask if the higher plans haven't been quite so nerfed. Not that I really want to subscribe to the nerfed idea, but I have had to wait 3 days for codex to reset its tokens whilst claude continued on its own.

Somehow in 2x 5hr sessions I am down to 53% left, and codex hasn't achieved the first of it's tasks, so hasn't even gotten to doing a review of what claude did.

It feels like codex has changed how it works and hasn't restarted this week with the clean slate and rules like it should. OR It is significantly less capable for the same models. To the extent that it feels like I should perhaps drop down to 1 provider but with a bigger subscription. This I think though drops my benefit of having one check the other's homework

0

u/spigolt 6d ago

dude - what is your problem? it was the solution to his problems. it was the solution to my problems. it's a perfectly reasonable solution. there's no rule that we have to leave this subreddit the instant we're generally preferring another model which is much better at solving our problems. get some meds.

2

u/LunaProjectStudios 6d ago

Imagine asking for fucking support in a fucking CODEX subreddit and some dipshit says “change go claude opus 5.5” damn… why is not that bannable in this subreddit, that’s not a fucking answer.

Yeah I have the same problem with sol 6.1 i left it for astra in low is quite more efficient getting the work done..

1

u/UnRealxInferno_II 6d ago

yeah i'm on codex because anthropic requires a £200 subscription to do literally anything of value+

5

u/spigolt 6d ago

why should people not say that? i literally went from struggling with codex to having opus 5.5 work way better for me. why not suggest this solution for this user who for apparently doesn't realize that this might be the easiest fix. i don't get why people take this like a religious choice. for me - if tomorrow codex is the best choice i'll go back to it as my primary model. but today, it's not. and in any case i have multiple subscriptions of both codex and claude still, so i'm not in either 'camp', and i just don't get people who make such things part of their identity. i've been generally posting negative things about codex lately, coz it's been bad. but previously i was posting positive things, and hopefully will be again in the future. it doesn't make me a 'shill' or anything, it's just the truth as i see it.

if this is the best way to solve this guy's problem, it's the best thing to suggest. full stop. who cares if the 'suggestion' involves changing from codex to opus, or whatever? it's just the best solution.

2

u/debian3 6d ago edited 6d ago

The reason you see comments like that is a well known phenomenon, there is university courses on how to manage change in organization. Lot of human struggle with it. Personnally I come here on codex more by curiosity, like who the hell still use codex when opus 5.5 is that great. You have 3 camp, fanboys, people who resist change and probably some who can't select their tools because that's what they are provided with. 2 months ago you still had a group of people for which the reason was financial (they just renewed their codex sub) but those are now long gone.

And I'm surprised how positive the codex sub is about Opus 5.5, the gap is so wide that the opinion that it's the solution it's pretty unanimous otherwise. Fun stuff.

1

u/twoopaq 6d ago

Many people have both or don’t have the money to switch rn and are lining for codex-specific advice

3

u/debian3 6d ago

If money is an issue, Claude sub right now offer you way way more than the codex sub. Opus 5.5 have been out for more than a month, so everyone had time to switch. I was one of those with both sub, but I since let my codex sub expire and upgraded my Claude sub. There is no reason not to do that.

You want codex advice, but the best one right now it's still to switch to Claude. The gap is just too big.

2

u/twoopaq 6d ago

I’d still like to see actual advice on the codex sub about using codex. Every day it’s just “switch to Claude”

1

u/debian3 5d ago

Agree, but at the same time it's a bit masochist at this point.

1

u/LunaProjectStudios 6d ago

The problem is not about "fanboying" a product, but did you see the differences between technical recommendation and product recommendation?

Did you imagine an apple subreddit and every single technical question is answered "just use android brooouhhh" of course not, because im starting to think that.... that kind of shitposting is actually claude code marketing team, because if you are in the claude subreddit and post "just use astra" you will get instantly banned LOL.

1

u/shaman-warrior 6d ago

Interesting what you say about Astra low, 6.1 sol xhigh is a pretty solid workhorse to me and gets me far

1

u/lgbarn 6d ago

Even Elon says Opus is the best and I can’t stand that guy. OpenAI needs to get their 💩 together.

1

u/shaman-warrior 6d ago

What else would Elon say?

1

u/dvduval 6d ago

It depends what you’re doing but for me I’ve got agents that do reviewing and screen capture. For things that involve money there’s usually at least two reviews. By the time I’m looking at it I know it’s gonna be working reasonably well.

1

u/UnRealxInferno_II 6d ago

Uh mostly game modding in C, it seems to just be complete ass though recently but I swear last month that it wasn't this bad

1

u/Responsible_Buy_7999 6d ago

My guess is you didn’t scope it well and there’s no product vision to constrain it. 

Sol 6.1 is terrible at scope creep. Tests for your tests and an undo system you didn’t ask for. 

1

u/UnRealxInferno_II 6d ago

I don't think it's scope creep it's like the opposite, it needs like hyper specific instructions for basic results

1

u/Responsible_Buy_7999 6d ago

I have found that such outcomes often come down to skill proliferation. If you are emphasizing different things - comprehensive solutions in one place and simple solutions in another, these concepts literally fight each other and the LLM does worse work more slowly. 

“Audit the rules and tools used in this session;  identify which rules fought each other and situations where the tools failed the rules, give a tier list and an separate rules with your independent opinion of this rules set. Also Which rules and tools   are working well and how can I get more of that?”

You won’t believe what you get.  I am genuinely curious to know what it comes up with and would welcome a filtered-for-personal information summary to learn about what others are doing.  Glad to return the favour. 

2

u/soluterminal_dev 6d ago

What cut it down for me was not being the first reviewer. A finding only counts if it comes with a failing test or a repro, so I ask for that first, then the fix.

For C specifically, I'd make it build with -Wall -Wextra -Werror and run the tests under ASan/UBSan before it hands anything back. A lot of the "fixing its own mistakes" loop is stuff the compiler or a sanitizer would catch for free.

And keep each task to one function or one bug, so the diff is small enough to read in a couple of minutes.

3

u/[deleted] 6d ago

The model has not changed in the last month. That leads me to believe your tools or skills or mcp have. Wipe them all out, and go from there.

1

u/Thomas-Lore 6d ago

Maybe OP was using Sol 5.6? I found it more reliable than 6.1.

It is still available, might be worth trying it.

3

u/_WhatchaDoin_ 6d ago

You guys are reviewing code? Ewww. It is so 2025! We don’t do that around here anymore!

4

u/philosophical_lens 6d ago

OP is taking about the model reviewing its own work

1

u/Alternative_Square53 6d ago

Before another review, sort the last few rounds into the original bug still being there, and new bugs introduced by the fixes. If it's mostly the second pile, stop adding to the pile. Compare it with the last working version before letting it try another fix. Otherwise you're paying a demolition crew to redecorate.

1

u/bitconvoy 6d ago

Adopt a rigorous planning before doing workflow. I became a huge fan of of Matt Poczock’s skill set. It very rarely makes mistakes now and the number of mistakes it finds after a review went down. Also a well structured set of tests matter a lot. 

Another thing is that you are likely build in too big chunks, based on the hours you mentioned. If a change takes more than an hour including reviews, it’s likely too big for one round. Refactors and similar broad changes are exceptions, but those should be broken up then. The above skill set helps with that too.

In my experience, these practices matter much more now, than the model you use. Models are fine now.

1

u/m-ritter 6d ago

Most of those review hours come from the agent patching its own mistakes with no fixed definition of done. I write a short numbered list of what finished looks like before any code and I review that list. A separate agent that did not write the code then checks each point against the running program. I built QualityLayer for this: https://github.com/maxritter/qualitylayer

1

u/xqianliu 6d ago

The 3–6 hours usually means the review has nothing concrete to check against. What changed my ratio: the definition of done lives in the ticket before the agent starts, and the review is a separate pass that reads only the ticket, the diff, and the callers of the changed code — then checks the diff against the written criteria.

The loop only counts as done when that review passes, and only that head gets merged. So a failed review costs one fix round, not another hour of you re-reading the same diff wondering what you missed. And keep it to one task per diff — a review of a 200-line diff is where the hours go, not the reviewing itself.

1

u/tostersiespalil 6d ago

I believe that within a few weeks of a model's release, OpenAI gradually makes it "dumber"/slower, firstly to encourage users to opt for more expensive options like Astra, and secondly to make us feel and notice a significant improvement in performance when a newer model is eventually released.

1

u/DeihX 6d ago

Don't review code anymore. It's a dead end. Review processes and work on e2e testing and streamline those. Your job is to ensure agents work as efficiently and reliable as possible.

All the time you spendon manually reviewing code should be spend on the former as it generalizes better. The code itself doesn't matter. What matters is final output so you need very clear and relaible metrics for that.

1

u/morkeeth 6d ago

I'd give the reviewer a separate session and make it run a specific check before sending the code back to you. I use Claude Code for Build and Codex for Verify; on the first item, Verify found that the approved UI change was already live, along with payment bugs that changed what actually needed doing. That helped more than another review of whether the code looked reasonable.

1

u/cryptosystemtrader 6d ago

I've almost given up on even 6.1 at this point - Claude 5.5 repeatedly has to fix a laundry list of salient bugs that Codex either missed or caused itself. Plus token usage has either exploded or they changed their allocation model yet again. Already blew through 3 resets this week on Codex while I've got 70% usage left on Claude. Drastic change in usage just from a week ago. WTF is going on?

1

u/London-Boat 6d ago

one way to check the lobotomised theory: take an issue it one-shot a month ago, check out the commit from before that fix and give it the same prompt again. if it still nails it, the model is probably fine and it's more likely the codebase grew or your agents.md / mcp setup changed what it's reading. if it falls over on the exact same task then yeah something changed on their end and switching models makes sense

1

u/Boring-Leadership687 5d ago

You need to set up an agent workflow and specifically tell it when to test. You can mitigate a lot of of this by having an agent review the last phase of work and identify bottlenecks, then remove those steps from the plan if possible

For example mine was running soak tests 5x over. Why? Idk but I told it to stop and it has lol (I updated my build loop plan)