J

i try to build things

[J @xxJayyyyy]

here’s a simple fix

>enable the 5h limit for everyone but allow the more experienced users to disable through settings

>new users/casuals won’t dig that deep through settings to turn off

>exp. users turn off on day 1 and continue building

>save on compute

problem solved.

[Tibo @thsottiaux]

Tomorrow we will bring back the 5h limit for Plus accounts across ChatGPT Work and Codex. I had mentioned this a while ago, but then postponed it.

This is necessary as (a) the 5h limit allows us to smoothen the load on our compute, allowing to keep the plan generous in terms of weekly usage and (b) users on the Plus plan are relatively casual and new users, but then also just accidentally eat through their whole weeks usage and then are confused, making it not a great experience.

We are for the upcoming months keeping the 5h limit not enabled for Pro $100 and Pro $200 subscriptions.

[J @xxJayyyyy]

@HarshithLucky3 Digging their own grave if they do

Claude and China would be delighted

[J @xxJayyyyy]

A week ago resets meant everything

But now it doesn’t hit the same for Plus users

Now resets allow Plus users maybe 1 more hour (or less) to work until the 5hr limits stop you

I’m considering turning off Tibo’s post notis since there’s no point

The hype and energy is gone

[Tibo @thsottiaux]

We are reseting usage for all paid users of Codex and ChatGPT Work.

Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes.

Depending on how you use Codex, you should see your usage go between 10% and 50% further than before.

We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed:
- Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed.
- Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed.
- Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed.
- Automations. Some custom schedules could run more frequently than configured. Fixed.
- Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed.
- Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed.
- Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this.
- MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed.

We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess.

Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!

[J @xxJayyyyy]

@sattyyouneed Not codex if you want to be productive

[J @xxJayyyyy]

@TokenGremlin The resets are performative and for marketing

They said that Luna was so cheap and no point to meter

If that were true they would have given plus users near unlimited luna usage

Oh wait they do but for free users…

[J @xxJayyyyy]

@nicdunz They went out of there way calling the $20 plan full of casuals which is the most popular plan btw

Talk about dividing their paying customers into social classes lol

[J @xxJayyyyy]

at one point chatgpt said that lunamaxxing was extremely cheap for them and basically unlimited

if that were true then why would they bring back the 5h limit then introduce luna reserve on top of that

it would have been smarter to bring back the 5h limit but exclude luna usage

[Ananth @Ananth7e]

wait...is it real that codex now has a seperate luna reserve on top of your regular usage limits?

[J @xxJayyyyy]

@z9inet3en that’s great to hear I’m seriously considering trying out claude

never really used it before but this is the perfect opportunity for me and others to explore it

[J @xxJayyyyy]

here’s a simple fix

>enable the 5h limit for everyone but allow the more experienced users to disable through settings

>new users/casuals won’t dig that deep through settings to turn off

>exp. users turn off on day 1 and continue building

>save on compute

problem solved.

[Tibo @thsottiaux]

Tomorrow we will bring back the 5h limit for Plus accounts across ChatGPT Work and Codex. I had mentioned this a while ago, but then postponed it.

This is necessary as (a) the 5h limit allows us to smoothen the load on our compute, allowing to keep the plan generous in terms of weekly usage and (b) users on the Plus plan are relatively casual and new users, but then also just accidentally eat through their whole weeks usage and then are confused, making it not a great experience.

We are for the upcoming months keeping the 5h limit not enabled for Pro $100 and Pro $200 subscriptions.

[J @xxJayyyyy]

@rohit3a yep exactly they spent months marketing that the $20 plan was great value compared to claude code and once people starting joining they sandbag them

[J @xxJayyyyy]

@retrievaaaa the real goal is to make the $20 plan which is the most popular plan frustrating enough for the power users to convert to expensive plans

they need to somehow juice the numbers to get ready for the ipo

[J @xxJayyyyy]

@nwptz yep lol welcome to the permanent underclass

[J @xxJayyyyy]

@rohit3a that’s kind of my point

tibo says this is protection for casuals and new users but really it’s not

if they wanted to tame the users who use all the compute they should have brought the limit back for all plans

like u said the casuals are not frying the compute

[J @xxJayyyyy]

@UthaaleReDeva 1. the flowing resets are prob going to continue regardless its such an easy marketing/flex play

2. I think I qualify as an experienced user but I have never ran out my weekly limit if u do its a skill issue and thats kind of the users fault for not managing correctly

[J @xxJayyyyy]

@HyrumDolan spot on bts this was a play to force the experienced users to upgrade to $100 plans but they forgot that users could jump ship to competitors instead

[J @xxJayyyyy]

in 1 day openai managed to

>slow future growth

>call the bulk of its customers casuals (read: not important)

>kill its competitive advantage against claude/gemini/grok etc (no 5hr limit)

>create an easy opportunity for another company with compute to fill their shoes

[Tibo @thsottiaux]

Tomorrow we will bring back the 5h limit for Plus accounts across ChatGPT Work and Codex. I had mentioned this a while ago, but then postponed it.

This is necessary as (a) the 5h limit allows us to smoothen the load on our compute, allowing to keep the plan generous in terms of weekly usage and (b) users on the Plus plan are relatively casual and new users, but then also just accidentally eat through their whole weeks usage and then are confused, making it not a great experience.

We are for the upcoming months keeping the 5h limit not enabled for Pro $100 and Pro $200 subscriptions.

[J @xxJayyyyy]

@z9inet3en agreed not only did they call their users on $20 plans casual they are also killing the competitive advantage they had with no 5h limit against claude/gemini/grok etc

if claude fixes their models/usage soon chatgpt users will definitely think about switching to them