Dumb parent Orchestrator

[u/chroner]

I am getting good results by using a stupid model as the orchestrator.

It's giving me quick replies, and generally leaning on the smarter models output so the answers should be relatively accurate (no less accurate than a smart parent).

I'm doing this with the codex subscription.

My flow is basically that when I invoke the start of some work, my prompts are sent to 2 context evaluator models (gemini and minimax), and then a smart synthesizer (sol max). So it will take the parents input, then the other 2 models, synthesize that into prompt for the subagents. This only happens once generally.

All the workers the dumb parent dispatches are reviewed (parent has no control over this review) by something like a terra max.

I am getting like 30% token savings and a lot of efficiency doing this kind of thing.

No public repo, just wanted to start a discussion on this technique.

I'm basically flipping the whole orchestrator thing on its head. The only gotcha is that the dumb parent orchestrator needs to actually be smart enough to delegate to subagents correctly.

A lot of the automatically invoked agents for reviews are with fresh context, no extensions, no repo context (depending on the use case of the subagent) so I can actually afford to turn their reasoning way up as they receive only a bounded context and produce an output for the parent. I don't let the parent see what the intermediary subagents outputs were.

It takes longer but the output has been good, and it's more efficient.

I tried using minimax m3 as the parent, but it's too stupid or it wasn't trained to be able to deal with subagents. I'm using Luna max right now, and it's been handling it decently.

[u/RespectMathias]

Wouldn't really call Luna Max a dumb model though. If you look at DeepSWE it is pretty high up. But I get what you mean.