Live data from Hacker News

GPT-5-Codex

openai.com

51–60 of 144 posts

Re: GPT-5-Codex

#51
post #22

Earlier quoted context omitted.

So you're all saying suddenly codex cli w gpt 5 codex is better than claude code? Hard to believe

Not suddenly, it's been better since GPT-5 launched. Prompting is different, but in a good way. With Claude Code, you can use less prompting, and Claude will get token happy and expand on your request. Great for greenfield/vibing, bad for iterating on existing projects. With Codex CLI, GPT-5 seems to handle instructions much more precisely. It won't just go off on it's own and do a bunch of work, it will do what you…

Sounds like the difference between finding what needs to be done, making a plan, and executing on it remains something to consider and be aware of.

Claude Code has been a revelation and a bit of a let down the past 45 days.

Some open acknowledgement would have been great, but in lieu of it, it seems it's best to hop on a new tool and make sure you learn how to prompt better and not rely on the model to read between until usage is "optimized" and it no longer seems to work for those folks.

I've seen some interesting files that help any model understand a programming language as it's strong suit and it might not even be an expert in and how to best develop with it.

Re: GPT-5-Codex

#53
Question, how do I get the equivalent of Claude's "normal mode" in Codex CLI?

It is super annoying that it either vibe codes and just edits and use tools, or it has a plan mode, but no in-between where it asks me whether it's fine it does a or b.

I'm not understanding why it lacks such a capability, why in the world would I want to choose between having to copy paste the edits or auto accept them by default...

Re: GPT-5-Codex

#54
post #47

Interesting, the new model's prompt is ~half the size (10KB vs. 23KB) of the previous prompt[0][1]. SWE-bench performance is similar to normal gpt-5, so it seems the main delta with `gpt-5-codex` is on code refactors (via internal refactor benchmark 33.9% -> 51.3%). As someone who recently used Codex CLI (`gpt-5-high`) to do a relatively large refactor (multiple internal libs to dedicated packages), I kept running in…

Small suggestion on refactors into packages: Move the files manually. Just tell codex "they used to be in different locations, fix it up so it builds". It seems that the concept of file moving isn't something Codex (and other clis) handle well yet. (Same goes for removing. I've ~never seen success in tracking moves and removes in the git commit if I ask for one)

Does refactoring mean moving things around for people? Why don't you use your IDE for this, it already handles fixing imports (or use find-replace) and it's faster and deterministic.

Re: GPT-5-Codex

#55
post #47

Earlier quoted context omitted.

Small suggestion on refactors into packages: Move the files manually. Just tell codex "they used to be in different locations, fix it up so it builds". It seems that the concept of file moving isn't something Codex (and other clis) handle well yet. (Same goes for removing. I've ~never seen success in tracking moves and removes in the git commit if I ask for one)

Does refactoring mean moving things around for people? Why don't you use your IDE for this, it already handles fixing imports (or use find-replace) and it's faster and deterministic.

Not necessarily -- in the case I posted about, we first abstracted some common functionality to internal libs, and then further abstracted that functionality into a number of packages (so they could be used by other clients).

So it was part simplification (dedupe+consolidate), and part moving files around.

Re: GPT-5-Codex

#56

Question, how do I get the equivalent of Claude's "normal mode" in Codex CLI? It is super annoying that it either vibe codes and just edits and use tools, or it has a plan mode, but no in-between where it asks me whether it's fine it does a or b. I'm not understanding why it lacks such a capability, why in the world would I want to choose between having to copy paste the edits or auto accept them by default...

Usually I give it a prompt that includes telling it to formulate a plan and not not do any coding until I approve. I will usually do several loops of that before I give it the instruction to go forward with the plan. I like to copy and paste the plan elsewhere because at times these LLM's can "forget" the plan. I usually do testing at each major milestone (either handed off to me or do builds/unit tests.)

Re: GPT-5-Codex

#58

Doesn't seem ready for prime-time. I'll be impressed when it actually installs. npm ERR! code 1 npm ERR! path /usr/local/lib/node_modules/@openai/codex/node_modules/@vscode/ripgrep npm ERR! command failed npm ERR! command sh -c node ./lib/postinstall.js npm ERR! /usr/local/lib/node_modules/@openai/codex/node_modules/@vscode/ripgrep/lib/download.js:199 npm ERR! zipFile?.close();

codex cli has been out for 5 months with 170k weekly downloads - it's definitely 'ready for primetime' if you can get past your bug. I don't have that issue.

Re: GPT-5-Codex

#59

Question, how do I get the equivalent of Claude's "normal mode" in Codex CLI? It is super annoying that it either vibe codes and just edits and use tools, or it has a plan mode, but no in-between where it asks me whether it's fine it does a or b. I'm not understanding why it lacks such a capability, why in the world would I want to choose between having to copy paste the edits or auto accept them by default...

Usually I give it a prompt that includes telling it to formulate a plan and not not do any coding until I approve. I will usually do several loops of that before I give it the instruction to go forward with the plan. I like to copy and paste the plan elsewhere because at times these LLM's can "forget" the plan. I usually do testing at each major milestone (either handed off to me or do builds/unit tests.)

Yeah, no way I'm doing copy pasting or allowing it to vibe it.

I want it to help me come up with a plan, execute and check and edit every single edit but with the UX offered by claude, Codex is simply atrocious, I regret spending 23 euros on this.

I see the visual studio code extension does offer something like this, but the UX/UI is terrible, doesn't OAI have people testing those things?

The code is unreadable in that small window[1], doesn't show the lines above/below, it doesn't have IDE tooling (can't inspect types e.g.).

https://i.imgur.com/mfPpMlI.png

This is just not good, that's the kind of AI that slows me, doesn't help at all.

Re: GPT-5-Codex

#60
post #6

Earlier quoted context omitted.

Interestingly, "more steerable" can sometimes be a bad thing, as it will tend to follow your prompt to the letter even if that's against your interests. It requires better prompting and generally knowing what you're doing - might be worse for vibe-coders and better for experienced SWEs.

Yes, given a similarly sparse prompt, Claude Code seems to perform "better" because it eagerly does things you don't necessarily know to ask GPT-5 may underwhelm with the same sparse prompt, as it seems to do exactly what's asked, not more You can still "fully vibe" with GPT-5, but the pattern works better in two steps: 1. Plan (iterate on high-level spec/PRD, split into actions) 2. Build (work through plans) Splitti…

The best of both worlds would surely be for the LLM to write what you've asked, but also write comments about other things it could have done so you can consider those extra bits when you check the output.
Post reply on HN