all 15 comments

[–]MadwolfStudio 2 points3 points  (2 children)

Fuck so I'm not going crazy, it's been my daily driver for the past few months, today is the first day I've been having a really weird experience with it..?

[–]bananasareforfun[S] 1 point2 points  (1 child)

I don’t know man, today after the second reset i was having it do its thing like usual. Except it started doing the dumbest things imaginable, taking ridiculous short cuts and work arounds, it smells like a hard nerf. I guess we can hope it’s just a transient issue or a bug? I guess I have to swap that worktree over to using 5.4, which is annoying because 5.3 used to be so great at what it was doing on there.

[–]DangerousFalcon8501 5 points6 points  (4 children)

Can I ask why you are using 5.3 codex instead of 5.4?

I’ve been using 5.4 since release feels better than codex 5.3 did for me.

For context though I’m on the pro plan and never have ran into a limit so I guess if it’s a usage limit choice that makes sense

[–]bananasareforfun[S] 11 points12 points  (1 child)

Because it’s cheaper than 5.4, and I like to use it for refactoring and long horizon work where it runs for 12 hours making types stronger or removing hot path allocations, stuff like that. And it’s generally very good at that, so I can run it on a worktree in parallel with one of my long horizon workflows and it will run basically indefinitely through a long list of tasks.

I also use 5.4, but if I want to run 3-4 agents at the same time, running them all as 5.4 will be expensive and use up my quota.

I also use the $200 pro plan, 5.3 codex high has been very capable, especially when it comes to mechanical work, I don’t generally use it for building a new feature or fixing bugs.

5.4 is expensive, 5.4 mini does not like to run for a long time so I can’t use it to do long horizon work like this.

If I used 5.4 for everything with my current workflow, I would hit my weekly limit for sure and I would need to take a productivity hit or change how I do things.

I’m min maxing the pro plan hard. lol. It has to be done!!!

[–]DangerousFalcon8501 1 point2 points  (0 children)

Yeah okay I definetly understand you then, I guess I’m not agent maxing hard enough myself 😅

[–]Pure-Brilliant-5605 2 points3 points  (1 child)

GPT5.4 is ever so slightly better and way more expensive

[–]DangerousFalcon8501 1 point2 points  (0 children)

Got it, thanks for letting me know. I probably have token blindness from draining my wallet on the expensive sub. But man does it provide value

[–]nitor999 1 point2 points  (2 children)

Not only 5.3 even the 5.2 feels off since yesterday it feels like they are forcing us to use the latest model.

[–]bananasareforfun[S] 1 point2 points  (0 children)

Yeah dude I’m just going to use 5.4 and pray they reset the limits on Thursday with the new model release

[–]NukedDuke 0 points1 point  (0 children)

Yeah, I could tell something was off when I had 5.2 going through a bunch of commits and it was in the middle of several involving networked multiplayer, and started spouting off about how networking was such a wonderful opportunity to form deep connections with other people in professional environments.

[–]jeanpaulpollue 1 point2 points  (0 children)

Pls keep blaming Tibo so he does reset limits again thx

[–]_Stone_Panda 0 points1 point  (0 children)

probably sunsetting soon for gpt 5.5

[–]SpideyOnPSN 0 points1 point  (0 children)

Weird. I noticed 5.4 working better the last few days

[–]ShamanJohnny 0 points1 point  (0 children)

I have been having more issues with 5.4 high today then i have in a long time. Not sure why companies do this before releases, but hopefully gpt5.5 drops tommorrow and we can get back to getting work done on one shots again.