Instead of relying on a single monolithic LLM, this setup uses a router to decide if a task needs a frontier model or if the distilled local model can handle it, while simultaneously compacting tokens to strip out noise.
For those wanting a deep dive into the deployment, here is the basic CLI workflow:
- Build the simulation
Use your existing agent traces and an OpenRouter key to create the optimization baseline.
wmo build
- Run the optimization
This step handles the heavy lifting: training the router, executing token compaction, and distilling the chain-of-thought from the teacher model into your specialized student model.
wmo optimize
- Deploy the endpoint
Serve the optimized model to your application.
wmo serve
The real-world utility here is the continuous loop. As your agent generates more traces in production, you can feed those back into the optimizer to keep the smaller model aligned with the frontier model's capabilities. It essentially turns your production logs into a training set for a cheaper, faster version of your AI workflow.
If you prefer not to manage the infrastructure, there is a hosted version available at:https://experientiallabs.ai
Next Automated YouTube Pipeline: Python, edge-tts, and MoviePy →