‹ BackHN Continuity

Thread

Beating GPT-5.6 Sol on retrieval with 100x cheaper open models

415 points · 114 comments · moonikakiss

  1. mrinterweb · · focus · HN ↗
    There is so much opportunity for purpose built models like this. Ideally a harness should spin up a subagent to offload to targeted models for specific tasks like this. I know this is not a novel idea. Claude code does some of this by handing off the "explore" agent work to haiku. I just love seeing that specialized LLMs are being developed.
    1. foota · · focus · HN ↗
      I feel like the future is people building applications with tightly integrated LLMs that work hand in hand with the application's own lifecycle and code.

      I also didn't realize that people were using agentic harnesses for search, it's an interesting idea. If the context length is short enough it should be fairly cheap compared to running "normal" agentic coding workloads where you have O(100k) context length for doing almost anything.

      1. kumama · · focus · HN ↗
        castform founder here. that's a future we are really excited about too :) ideally, you can post-train the llm within the application itself, as it's being used. both interesting infrastructure & algorithmic challenges here
    2. Malp · · focus · HN ↗
      There are! Chroma has Context1, SID has SID-1, and you'd actually be surprised at how easy it is to post-train your own with pretty good pass@ recall@ ndcg@ etc.

      There's also Hornet who have shared some interesting talks & blogs lately. I don't know that I'd exclusively use agents for retrieval the way Neon outlines here as well. I think distillation similar to what ZeroEntropy has done for bespoke retrieval & reranking with _some_ agent manipulation on top-k results works better (IME).

    3. devolving-dev · · focus · HN ↗
      Models keep on improving though, so doesn't fine tuning become an ongoing task with ongoing maintenance burden?
      1. kumama · · focus · HN ↗
        (one of the blog post authors here) -> once you set up a finetuning pipeline, it's often trivial to rerun it on top of a new open weights model. so, it's orthogonal to base model improvements
    4. Razengan · · focus · HN ↗
      > There is so much opportunity for purpose built models like this.

      OpenAI etc could themselves do this, and maybe they already do? Where the public-facing interface delegates to multiple little goblins behinds the scenes

      1. mrinterweb · · focus · HN ↗
        Exactly. There could be a lot of value for inference companies to do this. Could save a lot of money being able to hand off highly repetitive known tasks to far smaller specialized models.
      2. kumama · · focus · HN ↗
        castform founder here. openai actually deprecated their finetuning apis a few months back weirdly.
    5. phainopepla2 · · focus · HN ↗
      > Claude code does some of this by handing off the "explore" agent work to haiku

      This is no longer necessarily true. As of 2.1.198 [0] (released July 1st): "The built-in Explore agent now inherits the main session’s model (capped at opus) instead of running on haiku"

      [0] <a href="https:&#x2F;&#x2F;code.claude.com&#x2F;docs&#x2F;en&#x2F;changelog#2-1-198" rel="nofollow">https:&#x2F;&#x2F;code.claude.com&#x2F;docs&#x2F;en&#x2F;changelog#2-1-198

    6. benjiro29 · · focus · HN ↗
      &gt; Claude code does some of this by handing off the &quot;explore&quot; agent work to haiku.

      That is not handing off to a specialized model, its just handing off to a lighter and interior model (compared to the parent model). That by itself can create issues like the lighter model not capturing all the data that the parent needs.

      The idea is that we get specialized models that are better then general purpose models. But its rare for a specialized model to beat a strong general model.

      There is a reason why we hear less about this idea of smaller expert models, because large strong models to the tasks just as good.

      And if the tasks is repetitive to the point that specialization is useful, you can get into a situation that your better off having a program written for that reputative nature, then delegating to other models. And then have the main strong model, deal with the (semi)cleaned up data.

      1. BikiniPrince · · focus · HN ↗
        You can register models with mcp. I think it’s an expensive solution, but it is available in the framework. I use a light weight bus protocol that lets agents interact and pass short messages with pointers. It’s very efficient.
      2. tyre · · focus · HN ↗
        &gt; There is a reason why we hear less about this idea of smaller expert models, because large strong models to the tasks just as good.

        Smaller models are cheaper, sometimes faster. I agree that the “we’re an LLM fine-tuned for X” hasn’t worked out because you can just train Claude to do X (and Anthropic will), but not burning Opus&#x2F;Fable tokens on dumb-but-token-heavy tasks is good sense.

        As we move from “integrate AI into Y” to “optimize the ROI on Y”, we’ll see more of this.

        1. kumama · · focus · HN ↗
          castform founder here. the roi optimization makes sense. i think there are lots of usecases for which even a 2% gain in accuracy can be quite useful. off the top of my head

          - high volume customer support. higher accuracy means fewer escalation, reducing labor costs - fraud detection. catching even one extra fraud attempt could mean a lot in savings - and ofc the classic ads use-case where at scale bps in improvement could mean millions in revenue :)

          1. simianwords · · focus · HN ↗
            Would a bigger model be able to beat yours if some effort were put into prompt?
            1. dkersten · · focus · HN ↗
              At what cost though? “Beating” isn’t enough if it costs 100x or even 10x the amount.
            2. kumama · · focus · HN ↗
              the bigger model would still cost more :) at the same time, i see prompting as being orthogonal to post-training. i&#x27;d imagine post-training a smaller model with a better prompt would make it perform even better
              1. simianwords · · focus · HN ↗
                yes, can you show me tasks where this is true?
      3. kumama · · focus · HN ↗
        castform founder here. while it&#x27;s &quot;rare for a specialized model to beat a strong general model&quot; today, i think the tech&#x2F;knowhow on how to do so is getting there. we see some early signs of this in industry e.g.

        <a href="https:&#x2F;&#x2F;shopify.engineering&#x2F;sidekicks-continual-learning-loop" rel="nofollow">https:&#x2F;&#x2F;shopify.engineering&#x2F;sidekicks-continual-learning-loo... <a href="https:&#x2F;&#x2F;thinkingmachines.ai&#x2F;news&#x2F;learning-to-replicate-expert-judgment-in-financial-tasks&#x2F;" rel="nofollow">https:&#x2F;&#x2F;thinkingmachines.ai&#x2F;news&#x2F;learning-to-replicate-exper... <a href="https:&#x2F;&#x2F;castform.com&#x2F;blog&#x2F;elsa&#x2F;" rel="nofollow">https:&#x2F;&#x2F;castform.com&#x2F;blog&#x2F;elsa&#x2F;

        at the end of the day, models are only as good as the data they&#x27;re trained on. and if one has access to proprietary data, it should yield specialized models that do better than larger general models

      4. nullbio · · focus · HN ↗
        &gt; The idea is that we get specialized models that are better then general purpose models. But its rare for a specialized model to beat a strong general model.

        Are you sure about that? I mean, MoE is basically an array of specialized models. This beats single-model general purpose performance.

        Clever routing systems also seem to indicate frontier or frontier-beating capabilities at reduced cost, such as Fugu.

        Further to this though, I think it hasn&#x27;t been pushed hard enough. We&#x27;re not going down far enough in the abstraction chain. Most peoples idea of &#x27;specialized models&#x27; is an LLM trained on a particular domain (like math vs coding vs creative writing), where-as it should be going lower-level than that and incorporating not only more abstract and smaller specializations of LLMs, but entirely different types of AI models, classifiers, etc.

        I also think the reason we don&#x27;t really hear much about this (yet) is because there&#x27;s no incentive for the best AI researchers&#x2F;labs to go down this direction because it&#x27;s better suited for local-processing over your entire codebase, but the labs all want you to perform inference on their servers and spend your money there, rather than spend your own compute to increase intelligence. They have a larger incentive to try and scale in different ways. We&#x27;ll have to rely on open-source for this one.

    7. oliver236 · · focus · HN ↗
      this is exactly what leopold talks about in situational awareness
    8. try-working · · focus · HN ↗
      yes, and this is why we need model routing
      1. kumama · · focus · HN ↗
        castform founder here: totally! we also think model routing is also a post-training problem i.e. getting a model to predict the difficulty of a task and match it to the right model -&gt; we&#x27;re gonna be sharing more on that soon :)
        1. dd8601fn · · focus · HN ↗
          I’ve been trying to do this with a pet project and admit that I’m getting terrible results. My small llm as a classifier&#x2F;router stage just isn’t getting the job done.
    9. nikcub · · focus · HN ↗
      There has been an over-obsession with frontier models and benchmarks. Most of the work will be done by task specific models. You don&#x27;t put Phds on the factory floor.
      1. bizzletk · · focus · HN ↗
        If the PhDs don&#x27;t cost very much more than your equivalent of factory-technicians but still get the job done, why wouldn&#x27;t you do that, at least in the blunt case before cost control rears up?
        1. polotics · · focus · HN ↗
          because they will take initiatives for localized improvements you don&#x27;t want them to take
      2. dwaltrip · · focus · HN ↗
        This only works if the tasks are actually specific and don’t benefit from broad competency.

        IMO, this doesn’t match most things that people use LLMs for.

    10. nullbio · · focus · HN ↗
      Yep. It&#x27;s a real shame that the labs are incentivized not to go in this direction. They all want to try and suck us into the cloud and take away full control and local processing, but there&#x27;s far more opportunity by building small AI systems and tools into the harness itself to make the models more intelligent.

      They naturally don&#x27;t like this direction, because it draws the intelligence away from their systems, and onto the local machine, where idea moats cannot be protected and hidden, and costs can be dramatically cut. Imagine though, how powerful our harnesses could be if the best researchers were thinking about how to utilize the power of the gaming GPUs that most PC users have (or can get), to supplement the frontier model processing. Instead of trying to have the frontier model do everything, the frontier model can serve as the orchestrator over all of the smaller dedicated harness models. Right now my rtx4090 sits there unused for most of the day while I&#x27;m paying for inference in the cloud... It&#x27;s such a waste of parallel intelligence bandwidth.

      I&#x27;m not just talking about LLMs either, most people seem unaware that there are a plethora of dedicated AI models for all sorts of conceivable pipeline usecases, from all sorts of classification tasks all the way down to things like code duplication detection. Right now the LLMs completely suck at cleaning up code and architecture, and a big part of that is because the frontier LLM cannot fit your entire codebase + all of its long-chain reasoning into the context window. But using small local models and tools bypasses this problem because small fast models can iterate over an entire codebase quickly. A harness that creates a big model bundle + routing system + DAG-based memory&#x2F;execution management over all of these has the potential to be incredibly powerful.

      Even better, building a framework around this concept and having the frontier model dynamically and adaptively generate the ideal execution system for any given task&#x2F;domain. We&#x27;re working on coding today? Okay, here&#x27;s a recipe we can use: ..., and it generates a local model pipeline execution system that it feeds all of your prompts through in real time by using pre-defined or shared recipe building blocks, etc... Lots of interesting possibilities.

    11. kinnth · · focus · HN ↗
      isn&#x27;t this also the threat to frontier AI houses? As in they want you to expend tokens in their ecosystem, but the optimization at 100x is their profit?
      1. kumama · · focus · HN ↗
        castform founder here. i&#x27;d say it&#x27;s a threat but the frontier ai labs&#x27; argument would basically be that the market opportunity for intelligence is infinite so it doesn&#x27;t matter. at the same time, i do believe there will continue to be a massive, growing market for big labs, esp for super-frontier use-cases. today that&#x27;s longer-horizon coding tasks but in the future it can be things like scientific discovery, etc.
    12. boonzeet · · focus · HN ↗
      This is how Sakana&#x27;s Fugu model works, achieving similar performance to Opus&#x2F;Fable with a mix of open source &amp; mainstream LLMs.
    13. drob518 · · focus · HN ↗
      IMO, purpose built or “adapted” models are The Next Big Thing. If I’m using a model to write Python code, for instance, I really want the 8B or 27B expert model for exactly that, which would also be runnable locally. I don’t care about the 1.8T model that can answer every query under the sun and that only runs in a remote data center.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.