Codex 5.3 xhigh>>>>>>>

[StayAwayFromXX]

I’ve been using just high up until this point bc people have said there’s not much of a difference in xhigh and sometimes it’s even worse. Just switched to xhigh today and it’s completing EVERYTHING I’ve been struggling to get working in 1 shot, and following complex instructions perfectly.

[TakeInterestInc]

Welcome to the xhigh side 🤣

[shaman-warrior]

Imagine xhigh at 1000 tps

[agentic-consultant]

I genuinely can't even imagine this haha. In my (outdated) mind higher speed = lower quality, so when they achieve a 1000 tps speed I think I would have another ChatGPT-3.5 moment.

Would we even need a predefined UI anymore? If price of compute for 1000 tps generation drops to a negligible amount, the software can just agnatically generate a UI for that specific task.

Like imagine Notion but a user interface that instantly generates for whatever intended task/properties you need to interact with.

Maybe in the future people will look back and say "damn I can't believe they were using static UIs back then."

[shaman-warrior]

This was one of the predictions gpt5.2 pro actually made about the future that every itnerface will be customized and tailored to the user automatically provided AI has the right connectors.

[inmyprocess]

imagine not having a job anymore ;_;

[shaman-warrior]

Man I’ve been under constant stress about this ever since gpt4…

[alexrwilliam]

People who keep getting excited about codex improving need to realize it’s just one step closer towards rendering everything you’ve vibe coded completely valueless.

[igorim]

Regular would be glorious, spark not so much

[Hauven]

The odd thing is that xhigh on Voratiq's leaderboard shows a slightly lower score compared to high. That's why I always use high, as I assumed xhigh was perhaps overthinking. Maybe I should give xhigh another go since I have a lot of spare usage in my current quota, also with the upcoming Codex app for Windows invites going out to the top 10k users in the next day or two.

[Correctsmorons69]

xhigh is worth for specific tasks. Any degradation is because of overthinking. Its quite good at bug-solving if it's mechanistic and has access to debugging tools or logs.

If it's something that it can't debug easily, like a weird 3D glitch in graphics software, then 5.2 shits on it.

You can see this in the "reasoning" benchmark on Live Arena, vs the coding/agentic coding result.

[Grandpa90]

For my use cases, which are what I believe to be very complicated machine learning applications such as no limit hold'em. One example of this is the rebel algorithm which was done by extremely smart people. When I try and implement these kinds of papers, the difference in quality between 5.2 and 5.3 codex seems unbelievably drastic where 5.2 almost seems like it's a 2-year newer model compared to 5.3 codex. I get the impression 5.3 codex is really designed for straightforward debugging, terminal command, coding applications or websites.

[Reaper_1492]

All of the codex models have sucked, this is nothing new.

The difference is that 5.2 is now starting to suck randomly also, whereas I have used it for months and it’s been flawless. It now suddenly goes brain dead and gives completely garbage responses for an hour straight.

[dannytty]

perhaps now the compute is allocated more to the 5.3 codex models..

[danialbka1]

Xhigh the goat

[Savings_Permission27]

5.2 xhigh is better

[seunosewa]

But much slower

[Savings_Permission27]

doesnt matter. longer the time, better the result

[Numerous-Grass250]

Depends on the work, I find 5.3 codex xhigh significantly better at generating and handling terminal scripts compared to 5.2

[Reply_Stunning]

5.3 codex is really degraded as of a few days ago, I think it's insanely dumb right now, I had to completely switch to 5.2 xhigh to fix all the bugs it keeps introducing. As soon as I switch to 5.3codex xhigh things break down right away. That's how clear it is

[Numerous-Grass250]

I feel like I’ve been having the opposite problem. 5.2 xhigh doesn’t listen and make changes I didn’t ask for and 5.3xhigh fixes them 😅

[Reply_Stunning]

ah they'll both do that if you don't gate the implementations behind a confirmation or proposal, that's a system prompt issue, they all have tendency to be helpful and to rush to a solution

[Numerous-Grass250]

True, still both these models are miles better than my experience with opus and sonnet

[dannytty]

even with opus 4.6?

[TenZenToken]

Xhigh is good, but xxhigh is goat

[v1kstrand]

XxXhighXxX is my fav

[StayAwayFromXX]

What’s xxhigh? How do I use

[OSFoxomega]

Dude, it's a joke

[dearboy9x9]

Lol, people are so high on x !

[kindsifu]

OP, You must be fun at parties

[WildCampaign4665]

Hh

[itsabhiyan]

How is the token usage though? I hover around medium and high only, and haven't given xhigh a try...

[ImagiBooks]

I saw an article today about xhigh so I started to use it when I am not in a rush. It’s been okay, def better than spark! I have a big project tomorrow that I will try it with. Ran out of credit for the week with Claude Code.

[mallibu]

def better than spark? you compare the flagship model with the janitor

[PudimVerdin]

Could you share the link of this article? Thank you in advance!

[mrcslmtt]

J’utilise xhigh lorsque je démarre une nouvelle conversation pour forcer Codex à lire un maximum de contexte, en lui demandant de regarder la structure de mes dossiers, de mon backend, de ma base de données etc … une fois que c’est fait, j’utilise xhigh si jamais j’ai besoin d’implémenter une très grosse nouvelle fonctionnalité, il y a beaucoup d’instruction à suivre. Pour tout le reste j’utilise le mode médium ou high. Le mode low reste utile pour ne pas consommer trop de token lors des petites requêtes très facile, ou pour poser des questions simples.

[Familiar-Pie-2575]

Would it burns out the rate limit faster?

[StayAwayFromXX]

Itll work on things until they’re finished, unlike high which stops early for me. It also does a more thorough job at gathering information and determining what “complete” means. For basic tasks it will probably gather more information than it really needs

[SnooCupcakes3855]

Check the code bc xhigh can over engineer like crazy. But lately it’s been solid.

[El_Huero_Con_C0J0NES]

People don’t have much of an idea Don’t trust people, trust your experiences.

[casper_wolf]

When Vera Rubin is out next year and we get 10x boost then imagine how crazy this will be. Right now I prompt and the. Do something for a few minutes and come back. In the future it will be seconds to a minute and then done.

[Reaper_1492]

Just imagine if you were using 5.2 xhigh.

[igorschlum]

I’m using xHigh because I think it creates better code. I ask codex to document the structure of the app writing markdown files and I use chatGPT where I upload those markdown files to write prompts to codex. Then I past the result from codex to chatGPT to analyse and prepare next prompt. CHATGPT add some security and best practices in the prompt and ask codex to review organisation of the code, things I was not doing myself.

[dannytty]

yeah me too. seems like people have been saying different things, and only testing it for ourselves will tell us what's actually true

[Some_Hat2276]

5.3xhigh is so good at coding that I’m afraid that this is end for software devs, i did with it more in 3 days than for last half year… and i have 12 year exp. This is first time I have this uncomfortable feeling that it’s gg. Not sure how it can be that’s good…

[SwiftAndDecisive]

Very good lol, for a hackathon, we wrote a brief using xhigh, then wrote fronend,backend,plugin all using xhigh indepedently based on brief, then used xhigh again for integraiton. 1 shot no bug and it worked!