9 comments

  • adrianco3 days ago
    Local models need to be tuned to work well so this looks useful. Seems to be for general purpose model serving. I’ve been using <a href="https:&#x2F;&#x2F;github.com&#x2F;adrianco&#x2F;retort" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;adrianco&#x2F;retort</a> to run experiments for coding models across 13 different programming languages to see which frontier and local models work.
    • SilenN3 days ago
      That&#x27;s cool, thanks for sharing!
  • anshad2u1 day ago
    Interesting approach. What does the cold-start phase look like for a new agent? How many traces or runs do you typically need before the router has enough signal to safely offload tasks from the frontier model??
  • jack_pp3 days ago
    Not sure I get it. The model you&#x27;re improving is local? If so how do you even calculate cost compared to an API
    • SilenN3 days ago
      Open source models.<p>wmo routes requests between frontier models and open source models that continuously train using Tinker. As the smaller models improve, more traffic gets routed to them.<p>Calculating cost is just tokens in&#x2F;out.
  • surround3 days ago
    The title is misleading. This is model routing, not distillation.
    • SilenN3 days ago
      Fixed formatting which will help with readability. We do routing, distillation, and token compaction.
  • digitaltrees3 days ago
    Cool project
  • yiyingzhang3 days ago
    Cool idea! How do you guarantee privacy?
    • SilenN3 days ago
      It&#x27;s open source!<p>We do have a platform we&#x27;ll be launching as well to manage training + serving for you which will require more diligent privacy guarantees.
  • rglover3 days ago
    Excited to play with this.
    • SilenN3 days ago
      Let me know if you have any questions!
  • Art96813 days ago
    The absolute best way to prove this works is by releasing a model that was fine-tuned with this method and then showing benchmarks depicting the improvement delta between the base model and the fine tuned one.<p>The work is not done. Then release it to the masses and wait a few days for the actual real world anecdotes.<p>Until then, this is noise.
    • SilenN3 days ago
      Valid criticism. Happy to answer any qs. We&#x27;re still working on solidfying results.
      • dang3 days ago
        Ok, I think it is in your interest to wait until you have more to show, and we&#x27;ll be happy to help you with reposting it once it&#x27;s ready.<p>Waitlists are against the Show HN rules (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;showhn.html">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;showhn.html</a>), and you&#x27;re likely to get a lot of community pushback if you post before there&#x27;s enough substance for users to sink their teeth into.<p>Edit: we eventually got a more substantive writeup from OP so I moved that text to the top and re-upped this thread.
        • SilenN3 days ago
          Thanks for the heads up, removed mention!
    • irishcoffee3 days ago
      Benchmarks are the ultimate consolidation of halnons razor.
    • teravor3 days ago
      [flagged]
      • dang3 days ago
        &quot;<i>Please don&#x27;t post shallow dismissals, especially of other people&#x27;s work. A good critical comment teaches us something.</i>&quot;<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;newsguidelines.html">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;newsguidelines.html</a>
    • Reubend3 days ago
      Yeah, this is just slop. No benchmarks, no concrete case studies, just some vibecoded &quot;platform&quot; to finetune models on your own traces.<p>Which is an idea that has some value, but also some weaknesses. And this implementation of it isn&#x27;t forthcoming with that concept. You have to really dig in to understand what they&#x27;re even talking about.
      • SilenN3 days ago
        Happy to answer any qs.
  • renezander0303 days ago
    [flagged]