Cheap builder + frontier reviewer loop matches flagship on 66 tasks at ~1/16 the cost ($0.05 vs $0.72)

KrystalUnity · reddit · 2026-11-11

The author proposes the Krystal Loop Protocol: a cheap model writes code in a sandbox, tests run, then a frontier model from a different vendor reviews the exact diff. Reviews cost 1.5 cents each because the reviewer only sees a small packet—task, diff, test output. The key rule: the reviewer can't just say "this looks wrong"—it must write a test proving the bug. Failing test = real bug, gets fixed; passing test = complaint discarded. Fixes get re-checked and re-reviewed until clean or a limit is hit.

Results on 66 CooperBench feature tasks, graded by hidden tests:

Honest caveats: the cheap model alone was closer than expected—the review added only 0–2 solved tasks per run. The win is mostly price, not score: in the best run the review caught 77 real bugs proven by failing tests (70 fixed) and never broke working code.

The loop mattered more for conflicting features: on 30 feature pairs, plain git merge worked on 2; two agents handing off via short structured messages got 28 working at 10 cents/pair (chat-based collaboration also hit 28 but burned 581 model calls vs 333); one frontier model building both from scratch managed 22 at $0.196—nearly double the cost.

The reviewer can also be a CLI subscription you already pay: Gemini, Kimi, Grok and Qwen reviewed identical output and landed within two tasks of each other; Gemini matched the metered frontier critic exactly (56) at under 3 cents/task in API-equivalent spend.

Everything recomputes from public receipts with no API keys (python3 -m bench.verify); rerunning the loop costs $3. Open questions the author wants grilled: is 66 tasks enough, will it break on real repos, and could a decent local model as builder hold the score near zero cost.

Original post →

More from coding & agent

coding & agent channel →