Recommended Optimal Concurrent Thread Count

What variant of Codex are you using?

App and CLI

What feature would you like to see?

TLDR: Display an estimated optimal concurrent AI thread count that is dynamically calculated based on real-time and historical AI turn time and human response time

I've been struggling recently with trying to optimize the number of active threads I have running.

I finally got my local dev environment setup to be completely parallelizable, and thus yesterday I went crazy with up to 6 threads at once.

But it didn't feel optimal. It seemed like my brain was thrashing because of the context switching, and eventually many of my threads went dormant as I focused in on only 2 or 3 at a time.

I was talking with Codex and thinking about how to optimize this. With some simple formulas, and understanding average AI turn time and average time I take to respond to an AI after a turn, it seems like we could start coming up with a dynamic number of optimal threads to run concurrently.

So my ideas is this: please start tracking these metrics, and expose them, and even provide an optimal thread recommendation based on that info.

I think this will become even more important once Codex becomes an always-running agent similar to OpenClaw. I'm hoping it will be able to essentially act as a project manager, scanning GitHub for the next most appropriate issue, and then spinning up the threads.

But the problem is that I think we need some kind of thread throttling in that scenario. And the metric I described above I think would be excellent to determine the ideal throttling.

And what's nice is that I could start measuring my own and my AIs' performance. Because as I attempt to vertically scale each thread by raising the abstraction level of the tasks, as models improve in capability and speed, and as my own brain improves in responding to AIs and context-switching, it would be nice to see my throughput of work actually increase.

Sorry this is long-winded, but I think it would be awesome.

Additional information

_No response_