Balanced
The daily-driver profile — a fast, cheap, capable worker with a flagship cross-family judge and automatic effort. Most of the quality at a fraction of the cost.
The brief: most of the quality, a fraction of the bill. The insight this profile is built on: the worker emits ~85% of your tokens, the judge emits almost none — so spend down on the worker and keep a flagship judge as cheap insurance. This is the sensible default for day-to-day work.
The config
{
"agent_engine_config": {
"pipeline_worker_model": "zai/glm-5.2",
"pipeline_judge_model": "anthropic/claude-fable-5",
"pipeline_triage_model": "deepseek/deepseek-chat",
"default_model": "zai/glm-5.2",
"allowed_models": [
"zai/glm-5.2",
"anthropic/claude-fable-5",
"openai/gpt-5.5",
"deepseek/deepseek-chat"
],
"auto_mode": "off",
"effort_auto": "on",
"reasoning_auto": "on"
}
}Why these choices:
- GLM-5.2 as worker — the price/performance sweet spot of the catalog: excellent coding at $2.20/Mtok out vs. a flagship's $15. On a Z.ai coding-plan subscription (one settings line) the marginal cost drops further still.
- Fable 5 as judge. A flagship verdict costs cents per verification and
is naturally cross-family to the GLM worker. The judge is where you
don't save. (Prefer OpenAI?
openai/gpt-5.5judges equally well here.) effort_auto/reasoning_autoon. The autos encode the sensible mapping — judge high, worker medium, triage low; thinking on everywhere except triage — and you stop thinking about it. That's their contract.- Swap-in: worker
gemini/gemini-3-prowhen your tasks need the 1M-token window (whole-repo comprehension) at the same output price class as GPT-5.5.
Feeling indecisive about the judge? Turn auto_mode: "on" and let stella
pick the best cross-family judge from allowed_models per run.
Run it
stella run "add pagination to the /orders endpoint and update its tests" \
--test-command "pnpm test orders"
stella --budget 3.00 goal "clippy is clean and the test suite passes"What it costs
| Task shape | Ballpark |
|---|---|
| Focused single-file fix | $0.02 – $0.10 |
| Medium multi-file change, one revision | $0.05 – $0.50 |
| Hard refactor / long session | $0.30 – $1.50 |
Roughly 5–7× cheaper than the maximum-quality profile on the same work, with the same class of judge watching the result. If runs start needing extra revision rounds on your hardest tasks, promote just the worker to Fable 5 for those runs:
stella --model anthropic/claude-fable-5 run "the hard one"— an explicit --model outranks the settings for that invocation, and
everything else (judge, triage, autos) stays put.
Watch $/resolved in the Observatory for a week before tuning further. Balanced usually wins it — but if your repo's tasks skew hard, the data will say so, and if they skew easy, the dirt-cheap profile may match it.
Maximum quality
Every dial to the right — the strongest worker, a flagship cross-family judge, high effort and reasoning everywhere it pays. For work where being right is worth dollars.
Dirt cheap
The minimum-spend profile — DeepSeek doing the work, thinking off where it doesn't pay, hard budget caps, and the free local-server escape hatch. Coding agents for pocket change.