Jev + Opus 5.5 routing cuts Opus calls to 1/20
Across 2,000 tasks, Jev picks the next action first and only 100 go to Opus for deeper investigation, with result caching and a one-revision limit keeping costs down.
NOBODY TALKS ABOUT HOW CHEAP JEV + OPUS 5.5 IS TO RUN 2,000 incoming tasks. 100 Opus investigations. 3 routing options and a 1-revision limit turn an expensive queue into a workflow using 20x fewer Opus calls Jev selects the next action before an expensive run begins, while Opus receives the relevant evidence and clear requirements for the work it needs to complete finished jobs stay recorded with their input versions, so an unchanged request returns its saved result instead of starting another paid investigation routine decisions follow defined routes, and related checks share context instead of sending the entire project through separate calls when a result fails, the next attempt gets the exact requirement it missed and the evidence needed to fix it, with one correction allowed track the cost of the whole process, including routing, retries, and manual fixes, so you can see what each accepted result actually costs the complete setup is in the article below, from the first repeat check to a Jev + Opus 5.5 workflow with a budget you can inspect ↓
This post quotes another post: x.com/0xnineinch/status/2108604801411879139