Researchers describe distilling multi step agent workflows (chains of expensive model calls behind today's smart assistants) into the trained parameters (the weights) of a small open weights model trained to mimic them. The lab result is concrete.
The bill for a smart AI assistant is usually a stack of bills. Behind every answer is a chain of model calls: one to plan the work, several to call tools, another to verify the result. Each call is billed by the token, and on a frontier model those tokens are expensive. A new arXiv preprint (arxiv abstract 2605.22502) claims that chain can be collapsed into a single small model, with the cost dropping by roughly two orders of magnitude and quality staying near the frontier.
The technique is called trace distillation. A "trace" is the running record of an agent workflow: every model call, every tool invocation, every retry, every intermediate piece of reasoning. The paper's idea is to take those traces from a frontier-model agent stack and use them as training data for a small open-weights model, also called a small language model, or SLM. Through supervised fine-tuning (SFT), the small model learns to reproduce the entire workflow end-to-end from one prompt. No orchestration layer, no per-step API bills. Just one local model call.
The result, according to the paper and the two independent reviews that have already echoed it (commonplace.workforcefutures.net, themoonlight.io), is "near-frontier quality" at roughly 1/100th the inference cost. "Frontier" here is the AI industry's term for the largest, most capable closed-source models. The paper does not pin that down to a single model or a single benchmark; both the model and the benchmark suite are part of what a reader has to look up in the full text, which is itself part of the story.
Two things are missing from that headline number, and a smart buyer should notice both.
First, the 100x cost claim is an inference-cost ratio, not an absolute dollar figure. Token prices move; small models still need GPU cycles; and a small model that has to be re-trained for every new workflow is not free. The paper measures the inference bill, not the bill a company actually pays.
Second, the lab-to-deployment gap is real, and it is the question the original Reddit thread (r/MachineLearning discussion) is openly asking. The original poster, a practitioner rather than a paper author, wants to know whether anyone has actually run this against production traffic. The thread is short on answers. There is no peer review, no production case study, and no third-party benchmark outside the authors' own setup.
That gap is the actual story. The paper is concrete enough to be falsifiable: small models can be trained on the traces of expensive agent workflows, and the resulting model can hit near-frontier quality on the benchmarks the paper chose. It is also narrow enough that the next move belongs to the buyers. Any vendor offering "distilled" agents should be ready to answer three questions: which frontier model generated the traces, which workflow family was distilled, and which evaluation suite the resulting small model was actually tested on. If those answers are vague, the 100x number is a benchmark claim, not a deployment claim.
Until at least one of those questions gets answered in production, treat the paper as a research direction with a sharp cost curve attached to it. The cost curve is the part the AI industry will copy fastest. The production validation is the part it will take longest.