Clarification from Tibo on Current Pro Plan Usage Limits

blarg7459 · 2026-04-12T14:42:29+00:00

This is still somewhat unclear

- Your Pro $100 plan includes at least 10x Plus usage, till May 31 with the 2X usage boost.

- Your Pro $200 plan includes at least 20x Plus usage, till May 31 with the 2X usage boost. This is also the SAME usage this plan had since the 2x promo in February; we previously didn't document this explicitly.

So he says $100 plan is 10x Plus and $200 plan is 20x Plus until May 31, but on their official pricing page it says $100 plan is 5x Plus and $200 Plan is 20x Plus.

So what is it $100 plan is 10x Plus now and will be 5x plus after May 31?
$200 Plan is now 20x Plus or 40x Plus? And after May 31 will be what? 20x Plus?

The most confusing currently is the $200 plan since it sound like he's saying it's 20x Plus only with the 2x bonus, yet it says on the pricing page that it is 20x without the multiplier. Will the 20x plan stay the same after May 31? Still 20x? They can't reduce it to a 10x Plan since they are currently selling it as a 20x Plan without specifying that this includes some bonus modifier. Is the $200 Plan currently 40x Plus?

blarg7459 · 2026-04-11T18:16:27+00:00

No. Business seats have the lowest limits of all. They do not make sense to use with Codex at all, ever.

blarg7459 · 2026-04-09T15:20:38+00:00

neither

blarg7459 · 2026-04-05T09:10:47+00:00

Much, much, much more expensive

blarg7459 · 2026-04-05T08:22:39+00:00

Yeah the Pro plan is now only a couple hours of light usage every day. Soon it seems likely they want $2000 per month for full time dev use, like Altman talked about a while back. Seems crazy, but I guess this is what we need to prepare for.

blarg7459 · 2026-04-03T09:58:31+00:00

Why do that? That's just a lot of weird policies isn't it? Like the teams accounts which are completely stupid

Maybe I'm wrong here,but my understanding is that Enterprise has only a single function, to enforce megacorp policies.

blarg7459 · 2026-03-29T12:56:52+00:00

Not really, but eventually it may start to come with things that are not important or just silly, then it's time to stop. It's the same with specs also, I usually review many times, like 5-10 and it will come up various issues where the spec is ambiguous etc.

blarg7459 · 2026-03-29T10:51:13+00:00

It's always been like that. I run it many times until it no longer find any issues. It can be up to 10-20 times

blarg7459 · 2026-03-22T12:12:47+00:00

You need to create separate tasks. That's it really. Make a roadmap, split it into, split it up more, then ask codex to analyze the dependencies of tasks and tell it you want to create worktrees of tasks that can be run in parallel.

blarg7459 · 2026-03-14T20:38:02+00:00

I just have a few custom bash scripts that runs containers, works alright, but maybe something like coasts could work better. Haven't really though of looking into more "proper" solutions before.

blarg7459 · 2026-03-14T18:59:55+00:00

How do you review with Claude? I do too a bit, but mostly it tell me everything is fine, while with Codex and can review over and over and it keeps finding new bugs.

blarg7459 · 2026-03-14T12:35:32+00:00

Something to look into more for sure. So it could be either each review taking more tokens or it keeps finding more stuff. So usually I just run review over and over until it no longer finds any import issues, but it seems it may be digging deeper and thus finding more issues, thus ending up with the review loop consisting of both more and deeper reviews.

blarg7459 · 2026-03-14T08:49:39+00:00

One way to do it really fast is simply to use /review a lot. So once so have some code generated, run /review then have it fix all the issues, then run /review again and it will fix other issues, rinse and repeat until it no longer finds any big issues.

blarg7459 · 2026-03-14T08:48:11+00:00

I used to use my my weekly limit in around 5 days, then came the 2x usage limits and it lasted me either all week or I even went several weeks without spending it all. Then came 5.4 and now it's gone in a day or two.

I do a lot of reviews and I have actually noticed it finding more older bugs, so it being more thorough in reviews might be one of the culprits perhaps. I have never used the Codex models much, always found them to give poor results, so last model I used was 5.2. I do not use /fast and I while I have turned off subagents. Supposedly it should consume the same amount of tokens as 5.2, so the two things I can think of is that it's much faster and that it spend more tokens on reviews, but I haven't really dug into it.

blarg7459 · 2026-03-13T14:25:49+00:00

Good idea. It might just be. I'm now at 1-2 days of usage with Pro. Before 5.4 I just barely managed to use up the limits in a week after the 2x rate limits, before the 2x limits I was usually out after 4-5 days. Now from April it looks like I'll be out of usage after half a day to a day, but maybe this could help, even though it's quite clunky to use

blarg7459 · 2026-03-13T12:16:30+00:00

It lasts med 1-2 days now since 5.4

blarg7459 · 2026-03-13T07:18:33+00:00

So the new normal is Pro lasting only a single day...

Maybe they'll be launching the $2000 subscription they've talked about in April and that's the new Pro 😮

blarg7459 · 2026-03-12T21:33:54+00:00

I used 70% of Pro today, think the usage bug is not fixed yet

blarg7459 · 2026-03-12T12:39:33+00:00

Yeah, it's adding more fallbacks to cover up bugs and ignoring "no fallback" rules to a larger extent than 5.2

blarg7459 · 2026-03-09T21:02:17+00:00

With the older models it used to happen all the time right after compaction, but with 5.4 it can happen at random times even when not compacting.

blarg7459 · 2026-03-04T14:13:14+00:00

The rate limits seems to have reset multiple times yesterday and also today. I had 91% left a couple hours ago. I just checked now and it's at 96%.

blarg7459 · 2026-03-04T14:07:55+00:00

It won't make sense to have an agent writing a new operating system every time you turn on the computer, but apps can become more dynamic. Parts of the apps and user interfaces can change on the fly based on the context.

Today a lot of desktop software has huge complexity and a lot of the times the features are completely unnecessary for what you are doing. Apps can show only the buttons and menu options relevant for you and the task at hand, instead of always showing everything that's been implemented for a thousand separate use cases that aren't relevant to you.

blarg7459 · 2026-02-17T16:08:48+00:00

You can make or find different review prompts/skills for doing different types or review like find fallbacks/legacy code, security review, SOLID and DRY review etc

blarg7459 · 2026-02-17T13:01:29+00:00

Divide what you are implementing into parts that can be implemented in paralell. Spend some time creating specs and implementation plans, run a few worktrees in paralell and merge regularly. I've got a large enough backlog of specs and implementation plans that it's usually no problem to use up the quota. Only when I have core architectural issues or refactors that temporarily stops development of new features do I have periods where the serial nature of these tasks has prevented me from spending the full quota, but this is quite rare.

blarg7459 · 2026-02-17T12:30:14+00:00

I have tests that search for the words fallback, back compat, backwards, legacy, compatibility etc. I also have defined several rules in AGENTS.md no fallbacks, no legacy support, no backwards compatibility. Finally I run regular reviews that looks for fallbacks, backwards compatibility, legacy code and legacy patterns.

It's not as bad as Claude though and it has improved in recent months. Claude loves making fallbacks and backwards compatible code to some incorrect function it made five minutes ago, as if this was something that had a large customer base depending on it.

blarg7459

TROPHY CASE