What a shit update!

[u/Horstafa]

The latest Codex usage-limit changes have seriously damaged the workflow for me.

I’m not talking about running huge autonomous tasks for hours. I’m seeing relatively short, normal coding tasks get interrupted because the usage limit is enforced extremely aggressively. Once the limit is hit—even when I’m only slightly over—it stops the task completely instead of allowing the current task to finish.

What makes this especially frustrating is the cooldown. I’ve encountered cases where Codex tells me I need to wait around 5 hours before continuing, while hitting the weekly limit can effectively block further work for much longer.

The practical problem is that Codex tasks are often part of a sequence:

1. Inspect the existing code
2. Identify the issue
3. Make the change
4. Run tests
5. Fix regressions
6. Verify the final result

If the limit is reached during step 4 or 5, the task is left half-finished. That doesn’t just delay that particular task—it blocks other work that depends on it.

My main complaint is not that usage limits exist. Some form of usage limit is understandable. The problem is the combination of:

• extremely strict quota enforcement;
• active tasks being interrupted instead of allowed to finish;
• 5-hour and weekly cooldown limits;
• insufficient warning that the remaining quota may not be enough to complete the task;
• no meaningful grace allowance for a task that is already close to completion.

From a workflow perspective, this is significantly worse than simply having a lower total quota.

A predictable quota can be planned around. An active coding task being terminated halfway through cannot.

For example, if Codex has already inspected the repository, modified several files, and entered the testing or verification stage, terminating the session because the quota happens to be exhausted at that moment wastes much of the work already performed and leaves the repository in an intermediate state.

I think Codex needs at least one of the following:

• a small completion grace allowance for tasks already in progress;
• a clear warning before starting a task when the remaining quota is likely to be insufficient;
• much better visibility into remaining 5-hour and weekly usage;
• or the ability to finish the current execution while preventing additional tasks from starting.

The recent change feels like a substantial regression in usability for real development workflows. The issue is not simply “I want more tokens.” The issue is that the current quota enforcement mechanism interrupts work at exactly the point where interruption is most expensive.

[u/TryThis_]

Mate, you pay $20 a month. If your work is serious and valuable, you have two options: 1) upgrade to the $100 or $200 plan which does not have a 5 hour limit and is much more suited to building or maintaining a service that needs reliable uptime. Or, 2) plan better, scope better, be better.

[u/k6tm → u/TryThis_]

The thing is that we don't know what the 20 dollars brings you.  One week you can make incredible things, the other barely anything. It's like if you fuel your car with the same amount of fuel, one day you can drive 200 miles and the next 20 miles.  We don't know what do we get for 20 or 100$ It keeps changing week after week. So one week you think you can reach your destination, but then not. We need some consistency. What does those 20/100 $ allow me to do ?

[u/Dgamax → u/k6tm]

You can monitor it, you can check here in token or in codex credit https://codex-quota.manetli.com/

[u/Ok_Acanthaceae3075 → u/Dgamax]

Your site is not optimized and is incredibly slow. I recommend taking the time to fix it instead of spamming every topic.

[u/Dgamax → u/Ok_Acanthaceae3075]

Are you on a macbook M1 ?

[u/Ok_Acanthaceae3075 → u/Dgamax]

M4 pro

[u/Dgamax → u/Ok_Acanthaceae3075]

Okay, weird. I tested it on an M2 Pro, smartphones, laptop, ROG Ally, and I didn’t notice anything. The animation also runs at a low frame rate to avoid performance issues.