That’s exactly what I do. I have about 8 different sub agents in total but vaguely: Opus medium as orchestrator and reviewer, Sol(high/medium)/Terra(max) as implementer. My set up looks at my next GPT reset date and dynamically enters FAST mode if I’m under achieving on projected usage.
Similar experience here. The spirals on long running tasks are out of control at times with hours going by without a conclusion.
Re:GPT‑6.2 Astra and Sol
by SOLAR_FIELDS on Tuesday November 17, 2026 @01:55PM
(#50536381)
They (OpenAI models) are very tuned to be depth first and you can coach them all you want to try to be breadth first but as that context window fills up on those long running tasks they drift back to their first principles, which means obsessively testing and verifying a singular task rather than proceeding to the next task on the list
If you're using a sufficiently flexible harness (perhaps your own) you can make conversations as branchy as you want.
I wonder if that depth-first/rabbit-holing tendency is why GPT models tend to be better at mathematics (my own experience) than code.
I’m not sure. It’s very easy to get lost deep in a wrong branch when you’re trying to solve a math problem. You have to intuit when to give up and backtrack, lest you end up going in circles.
They are much better compute for dollar though. I have hilariously started to just have an opus thread maintain Sol subagents to get the best of both worlds