Show HN: Optimize and serve models with Fable quality at half the cost

github.com

52 points by SilenN 4 days ago

Hi HN, we built world-model-optimizer, an open source tool to continually improve a specialized model for an agent.

It does this by simulating production tool responses through text world modeling (similar to QwenAgentWorld, summary here https://x.com/silennai/status/2073887455884058814).

We can then use this to train a router for frontier, OS, and local models (use defaults or pick which ones to optimize against).

wmo ingests agent traces, builds the simulation, embeds the traces, runs different models you choose against the simulation scenarios, and then uses a KNN for model selection (similar to https://arxiv.org/abs/2505.19797).

- Cache aware: cache is taken into account for the effective price in routing.

- Confidence gated: we don't deviate from the best fit model when paired evidence over retrieved neighbors is below 0.5 standard errors or on queries unlike anything in the fit set.

- Optimize for cost or quality: train a balanced, cost max, or quality max router.

Usage

`wmo build` creates the simulation (or add your own benchmark)

`wmo optimize` tunes the router

`wmo serve` starts the server and can run everything fully locally. The simulation and router can update over time as more agent traces are gathered and new models are added.

Router results vs Fable

- RouterBench: -66.5% cost, -1.7% performance, -24.7% latency p50. 77.5% of traffic to Sonnet 5, 16.1% Fable 5.

- TauBench: -44.5% cost, +6.3% performance, -20% latency. 83% to Opus 5, 17% to Kimi-K2.6 (over K3).

- Terminal Bench 2: -64% cost, +8% performance, -50.6% latency. Sonnet 5 is fully along the pareto front. Training a specialized router per task isn't cheap. In sparse data regimes the value can be "here's the best model".

We're working on sample effiient continual learning for agent specific models at experientiallabs.ai"

adrianco 4 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 https://github.com/adrianco/retort to run experiments for coding models across 13 different programming languages to see which frontier and local models work.

  • SilenN 4 days ago

    That's cool, thanks for sharing!

anshad2u 2 days 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??

  • SilenN 7 minutes ago

    Technically 0 because a) it ingests your already existing traces and does an initial training run b) in the app we'll have pre-trained routers you can start with that will then learn over time

jack_pp 4 days ago

Not sure I get it. The model you're improving is local? If so how do you even calculate cost compared to an API

  • SilenN 4 days ago

    Open source models.

    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.

    Calculating cost is just tokens in/out.

    • handfuloflight 24 minutes ago

      What are the costs to train and use the Tinker models?

surround 4 days ago

The title is misleading. This is model routing, not distillation.

  • SilenN 4 days ago

    Fixed formatting which will help with readability. We do routing, distillation, and token compaction.

yiyingzhang 4 days ago

Cool idea! How do you guarantee privacy?

  • SilenN 4 days ago

    It's open source!

    We do have a platform we'll be launching as well to manage training + serving for you which will require more diligent privacy guarantees.

rglover 4 days ago

Excited to play with this.

  • SilenN 4 days ago

    Let me know if you have any questions!

Art9681 4 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.

The work is not done. Then release it to the masses and wait a few days for the actual real world anecdotes.

Until then, this is noise.

  • SilenN 4 days ago

    Valid criticism. Happy to answer any qs. We're still working on solidfying results.

    • dang 4 days ago

      Ok, I think it is in your interest to wait until you have more to show, and we'll be happy to help you with reposting it once it's ready.

      Waitlists are against the Show HN rules (https://news.ycombinator.com/showhn.html), and you're likely to get a lot of community pushback if you post before there's enough substance for users to sink their teeth into.

      Edit: we eventually got a more substantive writeup from OP so I moved that text to the top and re-upped this thread.

      • SilenN 4 days ago

        Thanks for the heads up, removed mention!

  • irishcoffee 4 days ago

    Benchmarks are the ultimate consolidation of halnons razor.

  • Reubend 4 days ago

    Yeah, this is just slop. No benchmarks, no concrete case studies, just some vibecoded "platform" to finetune models on your own traces.

    Which is an idea that has some value, but also some weaknesses. And this implementation of it isn't forthcoming with that concept. You have to really dig in to understand what they're even talking about.

    • SilenN 4 days ago

      Happy to answer any qs.