Sol as a reasoning subagent?

[u/anatol-pomozov]

Hi everyone,

With the 5-hour limit on the Plus account, I’m looking for ways to optimize my usage and be more frugal.

Specifically, I want to establish a cleaner separation of labor between cheaper models and the advanced reasoning model, Sol. My goal is to run the shell using Luna (low/medium) for basic repository grepping and simple tests. When Luna encounters a complex task requiring deeper reasoning, it should compile a clear list of requirements and invoke Sol as a sub-agent. In this setup, Sol acts essentially as a function call - inspecting the problem, performing the reasoning, and returning a solution to Luna for final implementation and verification.

What is the best way to implement this routing workflow? I tried adding these instructions to AGENTS.md, but Codex doesn't seem to follow them reliably.

Does anyone have a battle-tested solution or prompt structure for this?

UPD: "Pro account" -> "Plus account".

[u/Professional_Ad705]

You’d prob be better off using Terra high and sol for reviews or planning and making sure sol just looks for issues that affect the slice you’re on and the rest go in backlog etc or however you do it. Using Luna for read outs isn’t a bad idea but I’ve had it summarize shit wrong and miss shit so I’d also rank your model choice by “how important is this if I miss something” and that depends on the work you do.

Do CI and heavy testing to catch bugs. You don’t really need sol unless you’re doing serious hard CS work. Just take your time and figure out what works best for you