71–80 of 144 posts
Codex CLI IDE just works, very impressed with the quality. If you tried it a while back and didn’t like it, try it again via the vscode extension generous usage included with plus. Ditched my Claude code max sub for the ChatGPT pro $200 plan. So much faster, and not hit any limits yet.
What?
Earlier quoted context omitted.
It is 100% true. And they are rapidly losing users to Codex. Charts were shared recently showing a massive migration underway.
Oh yeah, Sonnet performance has been in the toilet for me. They claim they've mitigated it but when 4.0 first dropped CC was really impressive, and now I constantly have to babysit it because any time it hits a challenge it'll just stop trying and make a simple toy version and declare false victory. If I don't catch it and I let it build on top of that bullshit, things get nasty in a hurry. It's a shame because the p…
Earlier quoted context omitted.
So you're all saying suddenly codex cli w gpt 5 codex is better than claude code? Hard to believe
It is 100% true. And they are rapidly losing users to Codex. Charts were shared recently showing a massive migration underway.
Codex CLI IDE just works, very impressed with the quality. If you tried it a while back and didn’t like it, try it again via the vscode extension generous usage included with plus. Ditched my Claude code max sub for the ChatGPT pro $200 plan. So much faster, and not hit any limits yet.
Codex CLI IDE just works, very impressed with the quality. If you tried it a while back and didn’t like it, try it again via the vscode extension generous usage included with plus. Ditched my Claude code max sub for the ChatGPT pro $200 plan. So much faster, and not hit any limits yet.
>CLI IDE What?
Earlier quoted context omitted.
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…
Codex CLI of course will sometimes do the wrong thing, or sometimes do something extra that you didn't intend for it to do. It seems about half my sessions quickly become "why did you do that? rip __ out and just do ___". Then again, most of the other sessions involve Codex correctly inferring what I wanted without having to be so specific.
GPT5 + Codex CLI has been pretty productive for me. It's able to get a lot right in a simple prompt without getting too distracted with other crap. It's not perfect, but it's pretty good.
I actually worry GPT5-Codex will make it worse on that aspect though. One of the best parts of GPT5/Codex CLI is that it tends to plan and research first, then make code.
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…
So you're all saying suddenly codex cli w gpt 5 codex is better than claude code? Hard to believe