Using Jev as the control plane so Opus only handles hard judgment
File selection, effort allocation, tool-failure handling and test timing are all handed to Jev as typed results, cutting Opus spend by roughly 5x.
THE MOST EXPENSIVE MISTAKE IN AN OPUS AGENT ISN’T USING OPUS. it’s using Opus for every decision. I moved the control plane to Jev. Jev now decides: → which files and notes enter the context → how much effort each task deserves → what happens when a tool fails → which tests run and when the loop stops every choice comes back as a typed result. the host validates it before anything executes. Opus only sees the part that actually needs judgment. reported result: → same tasks → same results → roughly 5× lower Opus spend the breakthrough isn’t making Opus cheaper. it’s shrinking the decision surface that reaches Opus at all. Jev runs the control plane. Opus owns the hard reasoning. stop paying reasoning prices for routine decisions. the exact setup prompt is below ↓
This post quotes another post: x.com/noisyb0y1/status/2102309802072272956