Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A week of using Codex more than Claude

allaboutcoding.ghinda.com

Post reply on HN
Print view View original

111–120 of 311 posts

Re: A week of using Codex more than Claude

#111

Post by skeledrew »

bryanlarsen wrote: post #110
skeledrew wrote: post #88

Earlier quoted context omitted.

> useless, noisy and confusing That's your perspective. For Claude that's an extension of its thinking, which makes it work better. Just like the person who takes notes so they have references for later. Take it away and you're negatively impacting outcomes.

No, it's the other way around. If you put a comment "don't do foo" in your code, you're biasing future readers, human or artificial, to think about foo when you explicitly want them not to.

It isn't about making readers not think about foo. It's about biasing thought about foo in a particular direction. And I've seen it work multiple times: agent mentions it encountered X comments in the code and revised its action as a result (yes, I read live agent transcripts).

Re: A week of using Codex more than Claude

#112

Post by esalman »

kev009 wrote: post #105
esalman wrote: post #104

Earlier quoted context omitted.

So it's a problem when a poverty striken nation expect aid to combat child mortality, but shelling out $150m on Juicero or $500m on Theranos is fine? Please try to answer without sounding like a psychopath.

Whatever point you are trying to make is not coming across, what even are these numbers and what do they have to do with citizenry of the United States? You also have a quantum view of the United States that it is and isn't impoverished, so it's supposed to liquidate to fund some other foreign entity that is not rate paying? I'm dizzy.

It's probably not coming across because you're looking up too many synonyms.

Re: A week of using Codex more than Claude

#113

Post by skeledrew »

rplnt wrote: post #100
skeledrew wrote: post #87

Earlier quoted context omitted.

It's likely not helpful to you, but it is to Claude. Basically a memory entry at the exact point of relevance, with the same caveats. One advantage though is it survives cloning, so another using the project benefits.

It's only helpful to Claude in that it wastes more tokens and costs more.

It does visibly use a few more tokens in the short term. But it hurts Claude's ability in the long term if removed because it has to either think more every time it encounters that section in the code (more invisible thinking tokens used), or there's an increased risk of making a maladaptive change without context. Heck I've been bitten enough times already by it, though more recently it's cross project concern where Claude rediscovers some root cause that was already found and documented (I have it save a centrally-located writeup for things that took serious work to learn, when I remember, but I still need to make that knowledge pool known to other agents/sessions without having to manually prompt each time) elsewhere.

Problem is today's LLMs don't have the long term memory that humans have, and so remembering the reason behind a given change/decision has to be preserved in some way if it's non-obvious. Hence why there is {AGENTS|CLAUDE}.md, the auto-memory system, and 1001 variants of memory implementations in the wild. All are trying to ensure that LLMs can have the context they need at the location and time they need it. And you want to block Claude from using a technique that it natively finds helpful.

Re: A week of using Codex more than Claude

#114

Post by kev009 »

esalman wrote: post #112
kev009 wrote: post #105

Earlier quoted context omitted.

Whatever point you are trying to make is not coming across, what even are these numbers and what do they have to do with citizenry of the United States? You also have a quantum view of the United States that it is and isn't impoverished, so it's supposed to liquidate to fund some other foreign entity that is not rate paying? I'm dizzy.

It's probably not coming across because you're looking up too many synonyms.

"Looking up synonyms" huh? You have yet to make a coherent argument and keep trying to attack the messenger, typical behavior when people get called out for false entitlement. Your "psychopathy" accusations are pure cowardice.

Re: A week of using Codex more than Claude

#115

Post by elmer2 »

felixgallo wrote: post #64
trjordan wrote: post #31

Earlier quoted context omitted.

Not mentioning Grok 4.6 here is a crime. Fast and accurate. And it can communicate, unlike the gobbledygook that comes out of Claude.

[flagged]

I can't wait until you research the people responsible for Chinese models....

Re: A week of using Codex more than Claude

#116

Post by 0x457 »

skeledrew wrote: post #87
rplnt wrote: post #15

Earlier quoted context omitted.

> why something is there way it is It writes out stories describing what isn't there or what used to be there. It's usually not helpful, just noise. It also likes to write it in very verbose AI-styled prose.

It's likely not helpful to you, but it is to Claude. Basically a memory entry at the exact point of relevance, with the same caveats. One advantage though is it survives cloning, so another using the project benefits.

It's often is not helpful to claude either because it just confuses it more most of the time.

Re: A week of using Codex more than Claude

#117

Post by c0rruptbytes »

217 wrote: post #10

while everyone is somehow still stuck on and fascinated by claude, heres your quick update on the sota of coding models and harnesses mid august 2026 codex is good, both cli and desktop app, you get lots of usage on any plan. sol is good! and gets the job done, write or dictate a very long and thoughtful prompt, and leave sol xhigh or max fast working on it for an hour or so omp is an amazing harness, any feature cla…

Pi by itself is more than capable, OMP is okay but you really don't need much for a great harness (these models are RL trained to hell to be a coding agent, sometimes less is more)

I run a lot of SlopCodeBench - https://github.com/michaelasper/benchmarks

Fable/Sol/GLM 5.3/Kimi are its league (in that order) Deepseek/Opus is solid Qwen 27B is the floor - there's no reason to use Sonnet/Terra/Haiku

For everyday activity - I don't think you need to be using Sol (xhigh) for everything - unless you're made of money - I've found using Luna from OpenAI to be more than enough - it'll outreach to Opus/Sol when it needs to

Haven't had access to Gemini 3.7 but we're getting it at work soon, will give it a go!

Codex CLI is pretty bare bones in a bad way (at least Pi is extensible). Claude code is vibeslopped to the extreme

Re: A week of using Codex more than Claude

#118

Post by nsoonhui »

I used both.

Claude Code seems more generous with its quota, which is why I use it as my main driver.

That said, Codex does seem more capable, terse, and faster. There are some tasks that Claude can't handle but Codex can. One example was a WinForms binding/project deserialization bug. Sorry, the code is a mess, so even I couldn't quite figure out which part was causing which problem.

I initially thought the bug would be difficult to reproduce in a unit-test setting. Claude could only narrow down the problem and tell me where to put a breakpoint. Codex, on the other hand, actually managed to create a reproducible unit test first, and then used that to fix the bug. That impressed me.

The only problem is the quota. Codex burns through it very, very quickly, even when I'm just using Terra 5.6 Medium. That's basically why Claude Code remains my main driver despite Codex seeming more capable.

Re: A week of using Codex more than Claude

#119

Post by skeledrew »

0x457 wrote: post #116
skeledrew wrote: post #87

Earlier quoted context omitted.

It's likely not helpful to you, but it is to Claude. Basically a memory entry at the exact point of relevance, with the same caveats. One advantage though is it survives cloning, so another using the project benefits.

It's often is not helpful to claude either because it just confuses it more most of the time.

Confusion usually surfaces immediately, so it can be steered properly. Being sure of a decision that turns out to be wrong usually means a bug that could bite when you least expect it.
Post reply on HN