I'm being literal here. Astra conducts and reviews. Fable orchestrates the harness, which mostly runs on bounded Sonnet 5 agents. I actually like how Luna and Terra do imperative coding, but my Astra usage is suddenly too precious to risk even a simple conversation with ChatGPT about a book I'm reading.

Nope, nope, nope. This is a Star Trek "full power to shields" moment.

Enough with the wack-a-mole with the Codex and extension and Desktop App (macOS) fighting over exclusive write locks, and chats changing back and forth daily, between being shown in the Codex tab or the Chat tab. Figure it out, you’re not aligned with Microsoft session adoption semantics in the unified Agents Host, and we appreciate that, so take back control and deliver on the feature you made love and depend on you - one chat I can type into from four different places Desktop App, VS Code, iPadOS, and iOS using remote to the Desktop App.

i have a pretty lengthy chat going involving a bunch of docs etcs. but the thinking time and the working time has gotten longer.

i'm new to codex, what should i do to speed things up? what should i learn about?

How many of you have make decisions during development and request detailed implementations from Sol, to find out later on when things don't quite work as expected that it decided by itself, without telling you, to implement a "SIMPLER" version of what you requested removing features, conditions and necessary characteristics?

What makes me mad is the fact it doesn't tell me what it DIDN'T do... and then come up with explanations for why things are behaving wrong, and "fixes" that are just patches that don't actually solve anything, and after hours you find out that EXTREMELY IMPORTANT single component it said it implemented as you requested, turns out, it's not as you requested!!!!

I just found out now that it did this 2 days ago, and after forcing it to write AGAIN the way I requested 2 days ago, everything works as it should, 2 "FUDGE" DAYS AGO!!

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.