If you use Qwen3.8 27B to manage, to orchestrate, do do shallow research, and then make it ask claude you will notice that Qwen can get out of Haiku, Sonnet and Opus almost as good answers... I was researching how good the model asnswers where, I can't get to work with anything but Fable, but Qwen can get good work from any of them.
My theory is that if you make Qwen understand you, Qwen can elaborate as much as needed to get any of those models get good results, because it's filling in details.
So using Qwen to direct claude also get's you amazing results way way cheaper...<p>Update: let me elaborate more, I read the HN entry about the team of 5 Qwens being close to fable quality... so I embarked to add to my harness (<a href="https://github.com/alainnothere/privibe" rel="nofollow">https://github.com/alainnothere/privibe</a> because we all have one right?) and once I had added the orchestrate tool I had to now measure somehow it it's able to improve quality, so I claude and then Qwen to run a experiment to call my harness passing the model to use and ask them to do something, 3 rounds I think and see what quality came out of it... and as per the grading... qwen and claude agreed that the quality of the response comming out the harness using the orchestrate was VERY CLOSE, with opus and fable providing more "in my opinion you should" which matches my experience on why they are better.<p>One more update: I can't get copilot models to work decently, it may be my way of working... but I can get Qwen to follow what I try to do... if Qwen get's me he can then fire copilot cli and get amazing results by using copilot... bonus points seems like copilot cli is cheaper with the AIC (cost of the requests) so you can make the copilot subscription longer
I do the opposite of this, use Qwen3.8-27B as subagents, Opus 5.5 as orchestrator and planner, never implementer, and it cuts my token usage significantly. So it is using Claude to direct Qwen. Never thought of the other way around, will give this a try soon as possible.
Both of those orchestrations will work for sure.<p>Smart agent to orchestrate cheaper agents for labour.<p>Dumber agents to be very explicit about asking smarter agents for requests that require deep information.<p>This is a thing - the SOTA models really light up the more information you can provide them, and humans are too lazy / incapable of doing that in every prompt.<p>Entirely depends on what you are trying to do.<p>Edit: you can also use a smart agent to ask another smart agent, obviously, which is good for personal workflows.
Doesn't that muddle intent of the original prompt? If the smarter model didn't understand your intent correctly, the dumber one sure won't and it rephrasing and expanding the prompt will just amplify it's misunderstanding, no?
You wouldnt normally use a dumb model as a personal agent to get a smarter model to do work, but you may make use of that mechanism in some kind of automation process.<p>But there are definitely cases.<p>GPT Pro is an absolutely spectacular model, that almost cannot be used without 'prompt help'. Or rather, it can only be effectively leveraged by very intricate prompting, which requires the help of another agent.<p>I typically use Claude Code to write prompts for GPT Pro , and cut and paste the prompt in, and let GPT Pro work for 20 minutes, then take the response back to Claude Code and work with Opus to consider the results.<p>Opus is 'dumber' (nominally) then GPT Pro.
It could make sense to use a cheap model to decide if you need to run a long, high effort or otherwise costly effort. Then you can take many decisions at low cost, but think hard when it’s time to make an important decision.
>you can also use a smart agent to ask another smart agent<p>What's the best method to have a 'smart' agent just.. ask itslef?
Generally, you want a <i>different </i> smart agent as they have different strong sides (e.g. call Sol for a review from Opus)<p>You may use <a href="https://github.com/pingdotgg/t3code" rel="nofollow">https://github.com/pingdotgg/t3code</a> as a wrapper above claide/codex/pi/... harnesses, or a proxy below (forgot which one, as agent what theo uses for balancing multiple claude subs)
Just ask. The agents already know how. To boost it, have it read the exact docs that OAI/Anthropic provide.<p>Asking Claude to make prompts is like a Math teacher stuck working at a cafe about Math problem, the just light up.<p>They are very good at at it.
This is how I do it too. I run three levels:<p><pre><code> * Orchestrator: Opus 5.5
* Feature lead: GPT 6.1 Sol
* Worker: Muse Spark 1.3 Contributor
</code></pre>
As long as you have an appropriate project and sandbox for Muse Spark it's the real secret sauce for my setup and it's dirt cheap on OpenCode Go.<p>GPT 6.1 Sol is surprisingly efficient too, I've been impressed with it.<p>My orchestration skill setup is <a href="https://github.com/beefsack/processed-beef/" rel="nofollow">https://github.com/beefsack/processed-beef/</a>
Just one thing<p>Does anyone have any evidence that having the most powerful model being the orchestrator, and other sub agents being progressively less powerful, is optimal? Is this just common sense or it has been measured somehow?<p>For me it could be that this scheme may make the code itself poorly written, verbose or faulty
<a href="https://www.nature.com/articles/s42256-026-01268-y/" rel="nofollow">https://www.nature.com/articles/s42256-026-01268-y/</a> This is probably what you're looking for. TLDR; weaker orchestrator + strong workers scored higher than the reverse. Caveat with that, old paper: "High-capability models: GPT-5, Claude Sonnet 4.5, Gemini-2.5 Pro; low-capability: GPT-5 nano, Claude Sonnet 3.7, Gemini-2.0 Flash."<p>With that said, there is evidence that we recently crossed over a line for 'best practices' when it comes to systems of multiple agents. Comparing the shapes of 'n agents working collaboratively' vs '1 agent spawning n agents to handle distinct work', Opus 5.5[1] and Opus 5[4] performs better with the former, Sonnet 5.5[2] and Opus 4.8[3] performs better with the ladder.<p>[1] <a href="https://www-cdn.anthropic.com/fc1b44717c85dc068bc6ba5024219938094694bd/Claude%20Opus%205.5%20System%20Card.pdf#page=190" rel="nofollow">https://www-cdn.anthropic.com/fc1b44717c85dc068bc6ba50242199...</a><p>[2] <a href="https://assets.claude.com/870c8f525702625d2c62fc6dd04c857e3250bec1.pdf#page=123" rel="nofollow">https://assets.claude.com/870c8f525702625d2c62fc6dd04c857e32...</a><p>[3] <a href="https://assets.claude.com/0f0c97ad20d8005706296bd92aa1c27c6b2f4f61.pdf#page=213" rel="nofollow">https://assets.claude.com/0f0c97ad20d8005706296bd92aa1c27c6b...</a><p>[4] <a href="https://assets.claude.com/ceaf5c7ff2783855203fde8208ec311252dced5b.pdf#page=170" rel="nofollow">https://assets.claude.com/ceaf5c7ff2783855203fde8208ec311252...</a>
I think whether it's bottom-up or top-down, the core principle is still that you use cheap models for grunt work and use frontier models for expertise and direction.<p>In my setup, the orchestrator also drives a lot of the design and planning, and the less capable models get inputs from the more capable models by responding back up the chain. The more capable models also review everything that is produced by the cheaper models.<p>I've also had systems that invert this and allow cheaper models to call out to more capable models when they need to, but in my observation I found them quite bad at knowing even when to call out and I find wrapping the cheap models a bit more reliable in that problems tend to get caught before they bubble up to the user.
It sure saves tokens and even the 100$ subscriptions provide massive amounts of dev power. Also fair to note - mixing models is perhaps a good idea anyway as this way the entropy in them mixes and this supposedly improves result quality.
And which agent checks the work that the Worker does? If it's garbage then isn't that just extra tokens consumed by the Orchestrator or Feature lead?<p>I'd be interested to know what the difference in cost is in this setup on building a complex feature vs using Opus directly.
My goal was/is to have a local model as a "stable" part of the system, or at least a part of it that you have full control over, and have it reach out to the cloud for some Opus. In practice, to get results, I operate as you say.<p>At this point if I could do anything with zero effort or time, I would get Opus 5.5 to make a grand scheme, handoff to the local model, and give it ability to reach out to Opus again.
I do something like this by using old rule-based bot tech as the first layer you hit, and if it hits any situation it does not understand deterministically, it shells out for help to an external "smarter" agent.<p>That way you can do old school intent matching and rule-based bots that work super well, and only shell out for deeper work.
What do you use to get Opus to call Qwen?
I just fell Claude "there's an LLM server on this port serving this model, use it as a subagent"<p>Claude will write some scripts to call the LLM API and use it like any other tool.<p>I haven't found a pressing need for anything more complex than that. My multi-agent setups tend to be a pile of bespoke scripts per project anyway, an MCP server is only gonna get in the way. But I suppose this is because I self-host the models, if you're using OpenRouter or whatever it may need more complexity than a curl call to an unauthenticated port
So I use Google Gemini to plan or review; otherwise same loop so brain dumping how I get Gemini to Qwen/Gemma/Meta's model I forget the codename for; local agent reads the AI Studio log locally via Google Drive where they store the logs by default in a JSON format<p>So with the gdrive app for my OS it just looks like a local file path. Had the local agent learn to parse it.<p>I still prompt in AI studio direct as needed; local agents see the log change but cannot push back to Gemini their result.<p>Few reasons:<p>AI Studio is available where ever via browser, no VS Code or my usual vim setup to miss. I can switch between projects there as an idea hits and the agent switches up the local repo path and session history.<p>AI studio can search web, etc, etc already so my agent is less complicated with addons in general<p>Also using AI Studio between local agent turns has been my "human in the middle" approach; to have an explicit gap in the process and check each turn.<p>I only have a 24GB 3090 most models also take longer locally and I never hit the free tier limits with Gemini :D<p>Though the latest Meta model is twice as fast at 30B for me as other similar size models. 1-2 hour code gen and QA of build errors is now 30-50 minutes to parse latest changes from Gemini and get a successful build. The Meta model is pretty great at "fill in the middle" from a well structured plan.<p>Overall this loop feels like a normal workday pace. I freelance so I have a lot more say over that.
Custom MCP with a variety of functions, I have different Qwen profiles with a variety of subagent numbers and cache pools, my default is 192k pool with 64k initial context that can grow 32k at a time up to 128k, allowing 3x64k, 2x96k or 1x128k and 1x64k subagents. Qwen uses Pi harness. Model I use specifically is ukisai/Swift-1.5-Qwen3.8-27B-GSQ-RCO-GGUF
What hardware and inference engine do you use? On my Radeon R9700, at least with llama.cpp and some others, the GPU provides as many tok/sec with a single stream as with concurrent ones, so it's just as fast and supports longer contexts to swap contexts to RAM on turn boundaries.
Why not using a proxy in claudecode to forward all the claude-* model to anthropic as a standard proxy forwarder and route other models to other providers (openrouter, vllm, ..)?
This way Claude's model can get all the context from other models as all in the same harness.
To use other models than claude-* you can use agents files.<p>Ps: as you won't use your proxy to distill or alter claudecode requests to anthropic you should be compliant with anthropic rules.
Probably depends if you're trying to treat it as "subagent(s)" or as two different models working on the same stream of thought/context.<p>Both are, I think, valid options. Depends on the workflow you're looking for.
Try this out<p><a href="https://tysonberry-wogan.com/command-and-control-by-tyson/" rel="nofollow">https://tysonberry-wogan.com/command-and-control-by-tyson/</a>
Install the llm cli and tell opus to use it to prompt qwen.
you can easily run qwen locally in a pi harness (or similar) and just tell claude code to delegate all implementation work to it. claude will even setup the harness with the local model
You can have a setup like this with OpenCode agents, where you can define custom top-level agents, subagents, and assign specific models to each.<p><a href="https://opencode.ai/docs/agents/">https://opencode.ai/docs/agents/</a><p>There are a lot of ways to do this if you stop using Big Ai harnesses that make it difficult to use models besides theirs.
ohmypi will spawn subagents across different providers out of the box. Opus will spawn subagents running on my local ds4 installation just fine
> My theory is that if you make Qwen understand you, Qwen can elaborate as much as needed to get any of those models get good results, because it's filling in details.<p>How is this different than just telling the model you’re using to fill in the gaps itself?<p>If you’re not manually reviewing the intermediate hop, how does that add to the “understanding you”?
there is no difference... each case may be different, I have a local qwen gpu setup... and is fast... but not as fast as claude.
Fable is amazing and if it cost the same as my qwen setup I'll be running fable and never had qwen in first place.
But Fable is crazy expensive, Qwen is not as fast but cheaper... Haiku is fucking dumb IN MY HANDS... BUT my local qwen is quick enough to be briefed, get the idea and delegate.
I work with Fable mostly delegating to opus/sonnet and it's cheaper than just fable, I can't stand working with opus or the other models.<p>Why Qwen directing the others?
For the things claude refuse, Qwen can make very specific questions and still get an answer without triggering the thing.
I think that his idea is that a lot of preparation / setup work is boiler plate / brain dead stuff that can be done by a shallower model.<p>It's like, find the relevant scientific papers by using Google search and the scientific paper MCPs, summarizing stuff, etc. Then the big model can come in and actually think on the artifacts
Oh man I’m been playing with little -> big vs big -> little sub-tasking a bunch.<p>My sense so far is it’s very much about problem domain “taste” and there is no one correct answer (that is token cost efficient).<p>Does the smartest agent need the full flavor of the context of the problem to make real progress (i.e what’s been tried, how you’ve influenced the approach) or does the smartest agent really need a crisp problem definition and context room to really work.
> Oh man I’m been playing with little -> big vs big -> little sub-tasking a bunch.<p>I too wonder the same...<p>The real-world provides us many examples of such big -> little, or smart -> not-as smart workflows. For instance, we don't typically ask juniors or mid-level SDEs to design solutions to exceedingly challenging problems for a reason. However there are _some_ areas that those with less experience can tackle that is relatively risk-free if their work is reviewed by a more experienced engineer, which leads me to a conclude that it's task dependent.
I suspect that a lot of the fudging around with MCPs and tools can be delegated to smaller agents. Astra doesn't need to look at 300 websearch results directly or to extract text out of raw HTML
Anthropic has a native solution to this which is that you can use `/advisor` to adjust config to enable using Sonnet but set Opus as an advisor or use Haiku and then set Sonnet or Opus as advisor that the weaker model will automatically call when it thinks something warrants it:<p><a href="https://code.claude.com/docs/en/advisor" rel="nofollow">https://code.claude.com/docs/en/advisor</a><p>It allegedly will automatically judge when to call the stronger model, not sure how much instructions in prompts or AGENTS.md can steer it.
Thoughts on gemma?
Add this to the things I never imagined when thinking about what a world with artificial intelligence might look like.
[flagged]
[dead]
Everyone is discussing the tech, but you do realize that they made <i>mapping data to real people</i> easier using AI? This is essentially AI-assisted privacy violation, 4 times cheaper.<p>People, please <i>try to understand what you are building</i>. Don't just build it as asked!
Kind of offtopic, but I was kind of horrified by the rather blasé presentation of massive privacy invasion at scale, too. But there's clearly no stopping it technically, it will have to be handled by legislation, and the only hope of that happening is some kind of huge scandal.
You also need that for things like merging paper hospital records when you digitise them.
> Everyone is discussing the tech, but you do realize that they made mapping data to real people easier using AI?<p>That's Hacker News for you. They have chronic tunnel vision and are unable to look at implications that go beyond the technical. Particular blind spot for techno-social consequences.
What are you talking about, these kind of tech have been available in industry way before (eg hypertargeting / profiling in adtech), and is entirely unrelated to LLMs or Jev.
Found similar results, but the economics of the models involved have changed so quickly that it becomes so task specific on what the right thing to do was.<p>With an assemblage of models like Jev + Opus or Jev + Qwen, Jev would often do the right thing when deciding to escalate to another model - I was impressed that it would usually make the right call, especially if you gave it good awareness of what the other model capabilities were. "ESCALATE to opus if you need good vision awareness".<p>When Haiku 5.5 came out though, for my tasks, the cost differences disappeared almost immediately. Haiku was good enough / fast enough for so many things that introducing a decider layer didn't offer huge wins. Jev's "millisecond" level performance was nice but would get dwarfed by other latencies in my chain ( web browsing ), that it didn't make a measurable difference in my tasks.
This is very cool. But also, it’s a benchmark/result for a very specific experiment/task: identity resolution<p>Despite the title, the article is not making claims of, or demonstrating general usage improvements or general coding agent improvements
Not hard to test. I wired a “judge” into my existing Jev setup and… it works. I was able to trim my prompt down to the basics without “engineering” and have my entire test suite pass. Best I could get before was 1 failure, with an extremely brittle prompt. Like, adding a comma where grammatically appropriate broke 10 more tests.
Agreed, though many kinds of tasks are likely to benefit from this pattern, YMMV.
I like cheap intelligence but I don't like ubiquitous identity resolution. Perhaps my values are internally incoherent.
We have enjoyed a lot of privacy because of a lack of ability to violate it.<p>I mean that there was always the structural incentive to completely ignore privacy. It just wasnt technically feasible.<p>I wouldn’t assume any structural limit to what a government, corporation, etc wants to know about you. The day reading someone’s mind is possible is the day you realize the world doesn’t recognize any sort of right to private thought.
Let me make sure I'm getting this: They asked the models for answers but also for confidence score.<p>Jev's confidence score was more reliable. Which means that they were able to use Jev despite it having lower accuracy, because of the confidence was below a cut off, they would escalate to an expensive model (Opus)?<p>Whereas Luna, even though it was more accurate than Jev, its confidence was way off, so they couldn't reliably know when to fall back?
This sort of stuff has me believing that decision model controlled/prioritized context is the future of context management beyond the raw AGENTS.md file.<p>Why give all the context to an agent, when the context can also be curated, updated and made concise automatically for each new problem.
I too feel like context management has a lot of room for improvement, but the problem right now is that dynamic context management will most likely tank your cache hit rate. We need caching that's not just based on prefix-matching for this to make sense.
My bandaid fix for this is having a large number of sessions or "agents" and being ok with them being inactive at times, but they maintain their context. This has to be in some kind of system with appropriately sized "departments" to justify that agent's existence, or to justify it splitting into two, or creating sub-agents, etc. Yes, there is a cost when you cold start an agent after a week, but for now I'd rather pull that whole 400k+ context back without layers and layers of /compact. And then hopefully you keep that agent going for long enough to benefit from any cache-hit discounts.<p>Not really a good analogy, but it feels like having an image you like but every time you view it, it runs it through another loop of jpg compression. Use it when it's most effective, otherwise let it preserve it's details.
And as I see it that is impossible with current autoregressive global attention models because each part depends on the one before. Maybe if we can cache the local attention in blocks and only recompute the global parts.
Yes × 1000...
Jev is the classic type of scientific discovery, any human can see it's effectiveness without actually trying it. We were only deprived the discovery because of the incredible noises created by the AGI/ASI ferver....
most people only need if statements<p>wait till they found out about that nanosecond latency “conditional model”<p>turns out I’ve been an “RLIF” training expert my whole career
It's illustrative that there are even errors in how the humans have formulated the task and documented the errors.<p>They propose:<p>Valentino → Female Child<p>Yet this is obviously a boy name, else it would be Valentina. Is this model going to return confidence values? No, they want decisions. This is an inherent problem in AI with reductive logic for these tasks.<p>Likewise, dates. Is 17/08/22:<p>- 20170822 (Chinese write the year first, and in speech and chat they will say '17' not '2017'.)<p>- 20220817 (Everywhere But North America.)<p>Is 04/06/2009:<p>- 20090604 (Non-North American)<p>- 20090406 (American)<p>Without knowing the cultural context, the location, the document type, the document author, etc, you could be getting it wrong.
Germans write dates like 17.02.2026<p>It’s an interesting problem. And i have following thoughts to it?<p>- Are all cases even decidable?<p>- Shouldn’t one false positive rank higher than a hundred rank negative.<p>-Shouldnt’t the AI just abstain from decisions to avoid false positives.<p>- Is it smarter to seperate this in a lot of small sub problems and to define this as a rule set of small yes no decicions, why does this need to be solved agentically?<p>- You should definitely clean up deterministically first.<p>I feel like if you really want to solve this problem, you would approach it differently. This seems like a wrong approach and a bad article on top?
> - Are all cases even decidable?<p>No, and I think undecideable is quite frequent.<p>> -Shouldnt’t the AI just abstain from decisions to avoid false positives.<p>Yes, and I think regulation should be quite strong in this regard.<p>> - Is it smarter to seperate this in a lot of small sub problems and to define this as a rule set of small yes no decicions, why does this need to be solved agentically?<p>For larger contexts I worry about agentic confabulation, but humans unquestionably look at the gestalt when doing matching. I don't want idiot clankers making enforced decisions because they have misunderstood one field.<p>> - You should definitely clean up deterministically first.<p>If you can't do field validation on entry then I'm not sure deterministic rules work better, they may be worse, although easier to reason about.
But surely there are some deterministic reasons to clean up.<p>I personally wouldn’t lean towards LLMs on identity resolution. I would like give it the dataset and then ask me questions about specs? I really struggle to find the LLM part reasonable here. I mean potentially some typos, or nicknames, but those could be potentially resolved deterministically also.<p>I would probably have reviewer running that suggests new rules that I could implement. To me this seems more like compiler work than LLM work.
It’s a surname. (Edit you can see this in the first row they use it as an example surname)
>Is this model going to return confidence values? No, they want decisions.<p>The system doesn't return confidence values because that's not what they are designing. The models, however, do and to me it's interesting that Jev's measure of confidence is pretty well calibrated to its correctness.<p>>Without knowing the cultural context, the location, the document type, the document author, etc, you could be getting it wrong.<p>And? There's no perfect process, just ones that asymptotically approach correctness at exponentially increasing cost. They own the system and get to decide what works for them.
Exactly, there is no perfect process for such simplistic binary decision making. But we are seeing pipelines for tasks, like document processing, where it is becoming accepted that the machine is right.<p>Rather than binary classification we should be locating document fragments in a high dimensional feature space, and with all those fragments coming to a confidence bounded guess.<p>Additionally, when someone submits documents that can't be recognised as valid, the response should not be INVALID, it should be UNDECIDED. In that sense, passing to Opus is great, but passing a tiny fragment of the problem is a bad way to do it.
Excellent read. I use the same hybrid approach for a lot of security engineering work and it’s working well after initial calibrations, for example for our own harness we rebuilt auto mode exactly like this to judge tool calls and intent.
There is an error in your interpretation of calibration graphs and the conclusion that Jev is more calibrated than Luna is likely incorrect. Or at least the graphs aren't enough to conclude either way.<p>I don't have the actual data but based on the graphs I estimate the expected calibration error to be 2-3% lower for Luna on both the tasks.<p>Its true that Luna seems to give lots of high confidence values but it's also correct more. Higher number of mistakes at higher confidence isn't itself undesirable if its pass rate is also high. It'd be good if they reported actual ECE.<p>>Most of Jev's mistakes are closer to 50% confidence, which is what you'd expect out of a well-calibrated model.<p>This statement is also incorrect
The bar charts in this post really warped my head. If you’re interested in demonstrating confidence calibration you shouldn’t visualize the number of mistakes in a bar chart. Use a classifier calibration curve or something, but don’t just show me the counts in 10 percentage point buckets.
Ideally, "system one" intelligence is good both at quick reactions and at knowing when to hold off and wait for "system two." Sure enough, that works with Jev.<p>I don't usually get excited about the high-level, "whoooa man" marketing-speak, but the parallel is striking.
The most glaring downside with practically using decision models is if you need the model to not only decide something but give a reason, for every case, you end up not saving money or time, but just adding an extra step.<p>Give me a decision model that can do both, more expensive than today’s decision models but still cheaper than full on frontier model, and it’d open up so many more use cases, IMO
Where is the Jev that can replace 20 Opus sessions asking each other for help in a coordinated way? I want to shift towards a local model that "asks for help" in an effective way, but it still seems a bit out of reach. I mean, you could build your own 27B or 35B or A3B or bumblebee and spend a week or two carefully forming it into something useful, but it feels like that would be too specific and it would be thrown out when something like qwen4 is released. Maybe not, I don't know. Opus still exists as it is, in a "subsidized" form that's hard to step down from.
> Calibration matters<p>I agree. What I’ve encountered though is even building enough cases for a calibration data set is hard. And so we farm out to smarter expensive models like Astra to label cases and use that as a calibration data set for the now cheaper LLM judge actually running as our judge<p>Is this standard ? Or am I just too lazy to manually label enough data to calibrate ?
Jev is pretty cool for augmenting llms in a lot of ways. We use it in our own agent orchestrator[1] to help route ideas/prompts to running agent sessions. I find when I have a lot of parallel agents running its hard to reason about which agent I should be talking to and Jev makes that call for me.<p>[1] <a href="https://github.com/codealong/codealong" rel="nofollow">https://github.com/codealong/codealong</a>
Why isn't Jev on Bedrock asap... I did a demo for using it as an orchestrator but the problem is upper management won't approve it unless its on Bedrock which is a real bummer
What's interesting and annoying is that the results only matter for these specific releases of the models, with the specific parameters used.<p>That isn't obvious, unless you've been doing ML for a while.
Yep. It's actually kind of mind blowing how well "reasoning" works at de-biasing and pushing out of global minima, in hindsight, when you see how jagged things get again without.<p>These are the results of a little performance tuning/permutation testing run against context format and question wording we did. Obviously there is a lot of noise here but I was actually kinda surprised that there was a clear "best way to ask the question" even for relatively low N and low complexity/ambiguity of the task.<p>(This is a ~30s Ai-driven gif presentation of the results, the full grid shows up about 15s in): <a href="https://imgur.com/a/wGFZvGw" rel="nofollow">https://imgur.com/a/wGFZvGw</a><p>These models in particular have some pretty dubiously generalized and diverse training datasets. You can see this for yourself BTW by looking at the datasets SOTA Jev-like models are being trained against and evaluated on. No knock against the teams btw, I just think it's rather demystifying and makes me quite optimistic at how much better these models are going to get over the next few years: <a href="https://labs.baseten.co/articles/mammoth-1-and-elephant-1-frontier-decision-models" rel="nofollow">https://labs.baseten.co/articles/mammoth-1-and-elephant-1-fr...</a>
As an aside I'm amazed at just how fast the word Jev became generic. Possibly the fastest ever in corporate history?
You will depend on a super intelligent AI whose purpose is to take money from you
If you are looking at huge categorizing and parsing work, using a local decision model and passing it to Haiku or Luna can really lower your token cost.
Liked the read. I wish there were some code examples for how jev/Luna were actually done as I try wrapping my head around their new paradigm.
This is the Model Router architecture, from another angle. The problem is always, how does a dumb model know it needs to escalate to a smart model?<p>Some problems are obviously hard known-unknowns (eg “solve Navier Stokes”). The problem is unknown-unknowns or knowledge gaps, where the model doesn’t know they need help.
It's not a problem you can get right, because you can't know if you need to escalate until after you escalate (and what you escalated to disagrees with what your first choice would have been). But that's the point: how cautious you make the model is the knob that lets your trade cost for correctness.<p>I don't believe the answer is ever "how certain is the model?" It's "how much is at stake?" Or "how hard of a problem does this appear to be?" It's not about teaching the model to have uncertainty, but rather to be avoidant of things that are sufficiently important to get right.
> We tested whether fast, cheap decision models like Jev and GPT-6 Luna<p>GPT-6 Luna is a small LLM, not a decision model :P
No but it's the only OpenAI model with a decisions API <a href="https://developers.openai.com/api/docs/guides/decisions" rel="nofollow">https://developers.openai.com/api/docs/guides/decisions</a>
Small LLM + no reasoning + fixed JSON-only output = decision model
There's actually a decision model version of GPT-6 Luna...
You are right to be confused though.
OpenAI and their never ending naming games.
<a href="https://openrouter.ai/openai/gpt-6-luna-decisions" rel="nofollow">https://openrouter.ai/openai/gpt-6-luna-decisions</a>
I got very good results from JevK5: <a href="https://github.com/allebee/jevk5" rel="nofollow">https://github.com/allebee/jevk5</a><p>It's what I use locally. For my workload, it was right up there with Jev.
4x lower is so mathematically awkward.
That reads fine to me as a native-ish English speaker. What would read less awkward for you?
Like a comment on another thread, 0.25x would be the much better way to say this. It's 25% of the original value. It's also consistent: If 3x means 300% the original value, then 0.25x is 25% of the original value.<p>If you say 4x lower, that changes the semantics for lower than x vs higher than x, which is absurd.
> If you say 4x lower, that changes the semantics for lower than x vs higher than x, which is absurd.<p>where does it say in the rulebook that human languages have to have perfectly symmetric pairs of words?
Whatever happens, surely we can unite against the Crazed Barbarians who use percentages. :)
So like, -3x?
Thanks for making targeted advertising and surveillance state stronger. We love you for that.<p>Hope my sarcasm is making it across.
We've been doing this for a while. Fine tuning the decision model helps a lot too. The problem is you still need a pretty low confidence threshold (e.g 10%), but often times that reduces the work by 70% with 0% quality loss (in our benchmarks)
I wonder if something like this is the undisclosed new approach from Anthropic that presumably has massive improvements by combining multiple models. Leveraging decision models as much as possible seems logical for extra speed and token efficiency.
I think OpenAI and Anthropic have both been doing similar "routing" approaches for a while. Wasn't OpenAI one of the first to have a small model start responding to you for the first several tokens so that you got an instant response while the big model became available?<p>Similarly, Grok has been routing to Opus internally for a little while now I think.
> undisclosed new approach from Anthropic<p>Any source on that?
they do have the 'advisor' model setting now which also plays well with this
One of the most immediate and practical uses for AI for most (all?) businesses is CRM enrichment; this is a great article, thanks for sharing.
Been doing this on Discourse for Spam and locale detection, mostly doing d3-turbo with Qwen 3.8 Flash Next Help.
The application creeps me out
their cost numbers give you the hard set escalation rate even though they don't list it, (2.94 - 0.06) / 5.39 is ~53% going to Opus vs ~22% on the easy set, same thresholds
Seeing the title made me think: Jev used to be quite popular. Is anyone else still using it heavily these days?
I use swival.dev where a decision model (Cloudflare's Clef running locally is free and works great) is used for automatic model selection, but also to complete a task, just like the LLM. It gives confidence scores on the reliability of the LLM output, is used instead of the LLM, even mid-task when appropriate, etc.<p>And yes, that saves money since less tokens are sent to a remote LLM.
Isn’t that by nature a deterministic problem?
What about Sonnet? Haiku? Does it need Opus specifically?
i'm so numb to these headlines nowadays... i guess i've been disappointed by how effective these approaches end up being for actual work but i feel like it's easy to produce these headlines with "proof" that doesnt prove anything besides the sandboxed scenario it was run in
Jev is interesting because it adds "muscle memory" to LLMs. I think we're approaching some fusion of systems that approaches the human brain here.
[flagged]
[flagged]
[dead]
[flagged]
[flagged]
[flagged]
[dead]
[dead]
Memdoor author here which is a coding agent that run Jev inside. I believe this is becoming mainstream in any coding agent for routing calls and reduce input sizes. First candidates are edit tools for reading file or jgrep for greping large files folder etc.. The Token saving is mostly on the read side.<p>If we compare coding agents with Jev on vs off we get those numbers (metered with Memdoor):
- read-heavy tasks (coding questions , logs tail etc..): -63% to -65% input tokens, 40-45% fewer model calls, on GLM 5.3 half the wall time. Reproduced a month apart on two models (DeepSeek V4.1 Flash, GLM 5.3).
- a file edit: -23%<p>Two things match the post. Calibration is what makes it safe: I apply a decision at confidence >= 0.75 and fail below this threshold or on timeout or on an unknown tool family. The dollar saving scales with the price of the model being saved: on a $0.04/M model Jev costs what it saves so on a $0.38/M model it's negligible but on Claude model for example it can be outstanding.<p>Where it did not help: giving Jev more context about the repo. I found same thing as the post.<p>If you are interested i have put figures here : <a href="https://github.com/guregodevo/memdoor/blob/main/docs/features/DECIDE.md" rel="nofollow">https://github.com/guregodevo/memdoor/blob/main/docs/feature...</a>