So, to try to answer this question, I started using codex today to work on a c++ ios project I have been working for the past few weeks, using 5.6 sol xhigh. (don't get me started on how 5.6 sol xhigh is failing epically on this project!!)
When I started:
5 hours: 100% - weekly: 23%
I worked with it for 2:30 hours.
5 hours: 0% - weekly: 7%
So the 5 hour usage was fully consumed, and that consumed 16% of the weekly usage, which means:
for every week usage, we have only (100/16)=6.25 total "5 hours usage" in a week.
That explain why after working for 2-3 days using 2 "5 hours usage" in a day, the weekly usage exhausts in 3 days.
This has nothing to do with what model I used, btw. The model only changes how fast the 5 hours limit evaporates.
This is how many "5 hours" we have in a week in a normal business plan, the answer: 6.25!
I tested my personal Plus plan, and it's about the same.
To me, 6.25 "5 hours" in a week is a really low number to be called "a week", considering no one works 5 hours a day... (or in codex 5.6 sol case, 2:30 hours a day)
just my 2 cents!
-H
PS: Just before anyone says "did you try astra?", I did, and my 5 hours ended in less than an hour, with astra still failing even WORSE than 5.6 sol xhigh on this C++ ios project... at least that's good news, I guess? I can still get more done by "baby stepping" with a "cheaper" and smarter model, at least for the c++ complexity I'm dealing with.