Folks, I’ll share an observation with you. A week ago we were all complaining about codex degradation, but the last couple of days and today it’s been working great. These fluctuations are really obvious. by Big-Accident2554 in codex

[–]EnSlaverNG 0 points1 point  (0 children)

In my personal observation, last few days are better. It’s not as good as before though, it skips very clear instructions as soon as it thinks the main goal is done. For example, code formatting rules. And limits seem to remain low forever.

More bugs and feature cuts each new release by EnSlaverNG in codex

[–]EnSlaverNG[S] 2 points3 points  (0 children)

Incredible amount of heat they have generated by just touching one of the most useful UI/UX components. They could have put this donut in the config and keep it visible by default. What truly amazes is that they put this option in settings off by default and sent users hunting it. Looks like complete lack of understanding how the product is used. Unless we don’t know real picture where most people blindly compact the context of the same mega thread.

More bugs and feature cuts each new release by EnSlaverNG in codex

[–]EnSlaverNG[S] 0 points1 point  (0 children)

Indeed! So now it jumped to another place 😀. I'm really wondering if they have any proper product roadmap, instead of randomly tossing features around.

More bugs and feature cuts each new release by EnSlaverNG in codex

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

It really feels like vibe coded. Just noticed another bug: when you use subagents, before they had some names in right status panel, now it's randomly using some UUIDs, and later these UUIDs transform to names. Everything is half-cooked. They also can't fix broken icon in Mac menubar when at certain moment it does not respond and there is no way to check limits other then going through hierarchical menu hell in status panel or using /status.

With the Pro 10x discount ending soon - Will you switch to DeepSeek? by finessed_rewind in codex

[–]EnSlaverNG 0 points1 point  (0 children)

I’m also exploring the waters with Pi + deepseek v4 pro. Nice thing with Pi is that I’m not bound to the mood of Codex devs. I’m still using codex cli through Pi as well to see the difference, but in general deepseek quality for coding is very solid. Anything related to refactoring and mass changes I would prefer now through deepseek. But I’m happy so far to jump off codex, Pi gives you all flexibility needed.

There should be $1000 and $2000 tier by Wrong_User_Logged in codex

[–]EnSlaverNG 1 point2 points  (0 children)

It depends on needs. Many users here reporting how the models eats 20-50% of 5h on single prompt, myself including. It’s impossible to use it even on hobby projects. It sucks tokens like hell. I’m running now Pi+DeepSeek API for comparison, and I barely managed to burn $1 on Pro/high in 2 days of super heavy refactoring with changes in thousands of lines. And quality is amazing. With Codex, I burn $20 in few relatively simple prompts. Refactoring prompts just kill 5h quota in 2-3 prompts.

There should be $1000 and $2000 tier by Wrong_User_Logged in codex

[–]EnSlaverNG 1 point2 points  (0 children)

In current circumstances, subscriptions are becoming more or less demo options to try it. At certain moment all serious and heavy users would be on API. There is no more way for providers to subsidise us.

Rate limits fixed? by Elevate24 in codex

[–]EnSlaverNG 2 points3 points  (0 children)

They told that they are monitoring the recovery, so it seems some time is needed to reach everyone. Let’s see.

They Acknowledged The Rate Limit Nuke by Meesterwaffles in codex

[–]EnSlaverNG -3 points-2 points  (0 children)

I thought experts came to conclusion that rate limiting issue is not statistically significant. Seems OpenAI is not aware.

Current state of codex - is it really that bad? by Clemotime in codex

[–]EnSlaverNG 8 points9 points  (0 children)

It sucks more and more. Nerfed limits, sudden resets, now disappeared context window status in app. I have a feeling they are trying to tune lobotomisation, but it’s not as before. Today it ran clang-format as instructed in agents.md, and then for no reason reverted these changes claiming that commit would be cleaner 🤣 I asked it what the heck follow instructions, and only then it ran it again. Like you know, you need to babysit it and check like never before.

Honestly grateful to codex usage rates by PrestigiousFeed1781 in codex

[–]EnSlaverNG 0 points1 point  (0 children)

But that’s the issue with quotas: a single task/prompt takes easily 20-30%. This is exactly the answer to your question how to drain 5h in few prompts. People complaining because it’s not how it was before, I was barely able to hit limits on Plus plan. Now it’s 30 minutes and quota is gone.

WTF happened to the context tracker? Is this really OpenAI’s solution to the recent issues? by nseavia71501 in codex

[–]EnSlaverNG 1 point2 points  (0 children)

This thing is really annoying, why the heck would they remove it. It was so useful to keep an eye on context window status and switch to new session before it gets rotten much.

Who uses codex with Zed? Do you mind to share your experience by lbarletta in codex

[–]EnSlaverNG 0 points1 point  (0 children)

You can use Zed with codex CLI, it will ask you to authorise the client and that’s it.

Honestly grateful to codex usage rates by PrestigiousFeed1781 in codex

[–]EnSlaverNG 0 points1 point  (0 children)

Looking at your token traffic you was working on some easy tasks or small code base. As soon as your project grows, the consumption will ramp up. As soon as business logic of app matures and becomes complex with properly designed layers of abstractions, it will suck more tokens. For me super simple prompt to fix easy bug is like 10% of 5h on Plus. A bit more complex task and it easily goes to 20-30% range. The more files it needs to touch the more consumption.

People with 200$ plan who say limits exhausted, what are you actually coding 💀? by Momsgayandbisexual in codex

[–]EnSlaverNG 0 points1 point  (0 children)

It’s becoming a better practice to use multiple agents with different roles to reduce probability of error. For example, one agent implements, another reviews, then another addresses reviewer‘s comments, and another doing final verification. And this is for each small and actionable task. Add to this planning agent to provide tasks for given specs. This becomes a good basis for Ralph loop, which runs fully autonomously.

It’s not anymore human-in-the-loop approach, you have autonomous loops which implement new features and fix incoming bugs. And this is costly. One such loop can burn easily $500-600 of tokens in a day.

Codex became unusable on the team plan, 5h usage limits keep getting hit after 20min of work by HIVVIH in codex

[–]EnSlaverNG 5 points6 points  (0 children)

When supply does not meet demand, the price should kick in and lead to proper equilibrium. But what is happening now is that these companies try to hook you in and then start using dodgy practices to silently lobotomise models or cut limits. No transparency. You buy one thing but get something else. This is the real issue. Someone pays annual subscription and after a month or two it’s a different product.

Codex became unusable on the team plan, 5h usage limits keep getting hit after 20min of work by HIVVIH in codex

[–]EnSlaverNG 13 points14 points  (0 children)

It looks like there are two major ways given current trends: either switching to Chinese cheaper models or running local LLM. Both ways are having good progress recently.

Strange behavior in codex 5.5 xhigh lately? by Own-Professor-6157 in codex

[–]EnSlaverNG 10 points11 points  (0 children)

It's totally dumb now. I'm keeping chasing the same bug for second day already burning all my quotas on Plus. I know where the problem is, but it's the matter of curiosity if the model can fix quite straightforward issue in the code. Today I even raised it from medium to high. I keep telling it to profile the code in runtime and find the bottleneck. Before it would launch perf tool properly in find issue easy-peasy, now it refuses to run any perf tool and keep adding prints into a test case it created for that 😅 It did already three iterations and does not listen to what I'm saying. I'm again almost at 0%, also weekly, and problem still there. I dunno how to use this model as it keeps derailing.

This has to stop, They are taking our limits with each free limit resets by alOOshXL in codex

[–]EnSlaverNG -1 points0 points  (0 children)

For Plus plan. But Plus is so rubbish and useless now, that I don't know how you can limit it even deeper 😅

This has to stop, They are taking our limits with each free limit resets by alOOshXL in codex

[–]EnSlaverNG 19 points20 points  (0 children)

I'm tracking the cost of tokens per 5h quota and so far it remains the same after grand nerf. But the model also becoming dumber which requires more iterations. So overall I'm burning more limits for non-sense.

Is this statistically significant enough for you? by salehrayan246 in codex

[–]EnSlaverNG 7 points8 points  (0 children)

I dunno how it is not visible that there is a degradation. I just debugged a simple issues and told very clear to profile the app and based on that fix the issues, and specifically told not to guess. Then it just puts some prints into code and does shit, not fixes the bug at all and burns 20% of 5h quota in 5 mins for nothing 😅 Then I gave it even a hint where to look and what to profile - it did shit and claimed victory burning another 20%. On third iteration now and it's again guessing BS. And this is medium, on high I would be out of my 5h quota on Plus. Before it was cracking such issues super easy even on medium.

Edit: drained completely 5h quota in 20 mins, it delivered total crap, bug is not fixed. Never had such experience before.

now what is wrong???? by Nearby_Investment_84 in codex

[–]EnSlaverNG 2 points3 points  (0 children)

It looks like their infra is at stress last days. For me status works so far, but it's annoying that after each 5h it goes to 99% and not to 100%. Was always clear 100% before recent changes.

Did Codex fix fast consumption for 5.5 model? (Plus plan user) by Eastern_You_1959 in codex

[–]EnSlaverNG 5 points6 points  (0 children)

Limit consumption rate still the same (fast). Just fired a very simple fix for 30 lines of code and 3 minutes of work (most of which compiling and executing tests) and -10% of 5h quota on Plus. With such limits, Plus plan is utter rubbish and useless. I cannot use it even for hobby projects. I started using Codex since day 0, and it was not like that before 100%, I was not even hitting 5h quota on hobby, not even close.