
Just a pointer, pointing.
First time GSP owner, just turned two. It never ceases to amaze me how they are born knowing how to do this.

First time GSP owner, just turned two. It never ceases to amaze me how they are born knowing how to do this.
Feels like a long week already, comfort food incoming.
I’m a Claude refugee, and only been using codex for a couple of weeks now, so forgive me if you know all of this.
Firstly, credits last far longer. I’m used to hitting the limits on Claude regularly, so I code in bursts and do all the other work stuff while the clock runs down. With codex, this is doesn’t seem to happen much so it feels much more powerful, because I can use it when I want.
Secondly, I hit the 5 hour limit today with about 5 mins to go, codex was following a detailed plan and…. It carried on until it was done. Claude just dumps you out and you are left with dirty work half finished and you have to carefully restart at the right point when the clock resets. That’s a great feature.
Thirdly, I do a lot of planning before execution. I spend a fair bit of time on R&D and edge cases, so there’s a fair amount of exploration involved. With Claude, when it stops you’re just done until the clock resets. With codex I can hand off to ChatGPT, continue planning with repo access, get the next wave of implementation planned in fine detail down to the file level, then execute using minimal tokens when the codex clock resets. I can also use ChatGPT for busywork and documentation during that time.
It just feels like a significantly more useable product. I’ve dropped my Claude plan down to Standard and just using it for first pass code reviews of the work codex has done. It doesn’t find many problems.
I’m sure there’s nothing new here for most of you, thanks for listening.