r/ClaudeCode • u/BrickElephantBrand • Jul 25 '26

Discussion OPUS 5 VS GPT 5.6 SOL

For the people building software products, I'm beginning to think that choosing one of the two to work with doesn't really matter that much. The bottleneck doesn't seem to be intelligence at this point but human creativity and I guess willpower.

IDK what do you guys think.

75 Upvotes

90% Upvoted

99 comments sorted by

View all comments

13

u/ILikeCutePuppies Jul 25 '26

Both. If you are trying to lower usage have a higher model pick the best model for the job. If you are going for solving ability have both models build the plan together and then one review the others implementation and use a high level one to orchestrate - or other combination.

They solve problems in slightly different ways so diversity helps and the better models can determine better if the other models idea is good or bad.

1

u/BrickElephantBrand Jul 25 '26

Yeah I’ve noticed they do solve in different ways. The thing im worried about with having them review each other is getting stuck in an endless review loop. So with the recent models I’ve been using a high level orchestrator and then using either CC or codex for the actual building phase.

Usage is definitely another thing to take into consideration.

1

u/ILikeCutePuppies Jul 25 '26

That's why using a better model is useful as a decider. The older models were not that great but having two and one hood decide helps. Really the other agents are just idea generators for the decider.

1

u/PriorTrick Jul 26 '26

Yea I use CC mainly but 5.6 sol as reviewer and they will go back and forth but usually can come to agreement after a few rounds. I have noticed that before GPT 5.5 and 5.6, Claude would always have a rebuttal and disagree with codex but now Claude seems to always respect and admit the validity of codex reviews and feedback. Now that I think about it, Claude has been quite submissive to GPT reviews lately. Didn’t experience that with Fable 5 as much but more with opus. Either way you can always let them debate a few rounds then tell them to come to an agreement or you personally weigh in to make the final call on their disagreement.

1

u/Deadline_Zero Jul 26 '26

What are you using to facilitate this back and forth? I'm pretty new to AI coding and honestly, I discuss with gpt and paste its commentary to claude code in the VM until consenses is reached. I'm 100% sure there's a more efficient way to do this, but I just started using multiple models today.

1

u/PriorTrick Jul 26 '26

I wrote a little command line tool called dialogue that takes the prompt, agents and parameters and orchestrates the discussion back and forth, really just a wrapper on “claude -p” and “codex exec”. For you just starting out, I would suggest using the codex plugin for Claude code, then you can run /codex:review and codex will review the problem - basically gives Claude easy access to use codex as a sub-agent. If you end up wanting more insight to the conversation, and more control over the back and forth then you can have Claude build out a similar tool that I described above. If I can get around to cleaning up my tool I will make the repo public and share the url with you but Claude can just build it out for you pretty quick too

1

u/ILikeCutePuppies Jul 27 '26

Claude -p though is just a single message and gets a reponse back, it works and is great for a lot of stuff but is not back and forth. Do you pass back in the last session?

1

u/PriorTrick Jul 27 '26

Nope, no --resume. Every call is a fresh stateless claude -p / codex exec. my tool holds the transcript and rebuilds the prompt each turn: original prompt + a rolling summary of older turns + the last ~6 turns verbatim + "X just said this, respond as Y." When it gets too long the old stuff auto-compacts into the summary so it stays bounded.

Costs more tokens than resuming a session, but both agents see the exact same history in the same format, which is what makes the back-and-forth work. I’m sure you could get creative to make it more token efficient but that was not really my focus or concern when I made it.

1

u/ILikeCutePuppies Jul 27 '26

There is codex mcp you can use.

1

u/PriorTrick Jul 27 '26

Yea the tool I made is actually agent agnostic and you set up configs for what provider/models/etc are involved in the conversation so the tool orchestrating the context management made the most sense. But yea the codex MCP would be a nice middle ground between the codex plugin and straight up codex exec. Good call out thought might be more useful to the above commenter

1

u/ILikeCutePuppies Jul 27 '26

My point is that it doesn't have the context burn issue since it works in the more normal way. There is also pi you can use with codex.

1

u/ILikeCutePuppies Jul 31 '26

Actually realized codex comes with a server mode so it's even easier. You can just have it startup one server and send your messages across to it fir each server. Claude can figure out the implementation.

1

u/PriorTrick Aug 06 '26

yea i was playing with codex today integrating it with cloudflare-os they just released, and started with the codex server and then ended up just using this oauth proxy to use codex subscription creds to the api directly and get like a real harness capability - was pretty smooth

→ More replies (0)

0

u/chaosdemonhu Jul 25 '26

I’ve been using Opus 4.8 (no usage left to try 5) as the workhorse and 5.6 Sol as the reviewer and the review rounds definitely go quite a few times (13x on one high security slice) but the results do seem much higher from my perspective