cd /news/ai-agents/retrace-distilling-tool-using-agents… · home › topics › ai-agents › article
[ARTICLE · art-168496] src=huggingface.co ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

ReTrace: Distilling Tool-Using Agents into Planner-Free Workflows

A paper titled ReTrace presents a method that converts natural-language standard operating procedures and a few logged LLM agent runs into reusable code-driven workflows in which code, not an LLM, selects each next step. On 79 procedures from the authors' production platform, ReTrace workflows reached 93.8% completion versus 96.8% for the agent at 24% lower cost per task, and on τ²-Bench they reached 75.8% task success (agent: 80.6%) while running in 1.3s instead of 170s. Three rounds of repair on training failures lifted k=2 workflows from 66.7% to 81.2%, and on eight SOP-Bench procedures repair from labeled training failures raised ReTrace from 80.6% to 87.8% at 0.40s per task, compared to 85.5% in 46.6s for the agent.

read2 min views2 publishedNov 12, 2026
ReTrace: Distilling Tool-Using Agents into Planner-Free Workflows
Image: Hugging Face Blog

Papers

Abstract #

ReTrace converts natural-language SOPs and logged LLM agent runs into reusable code-driven workflows that cut cost and latency while maintaining competitive task success.

deepseek-ai/DeepSeek-V4.1-Flash Business process automation runs the same Standard Operating Procedure (SOP) again and again on new inputs. Large Language Model (LLM) agents can follow an SOP written in natural language, but they call an LLM to choose every step of every run, which adds latency and cost at scale. We present ReTrace, which turns an SOP and a few logged agent runs into a reusable workflow in which code, not an LLM, selects the next step. The agent's reasoning, the explanation it writes with each tool call, often states why it took an action; the tool calls alone do not. ReTrace extracts the condition behind each step, merges these conditions across runs into a compact rule document, and generates an executable workflow from it. Only this last stage depends on the platform, so rule documents can be compiled for different orchestration platforms. On 79 procedures from our production platform, ReTrace workflows reach 93.8% completion, against 96.8% for the agent, at 24% lower cost per task. On τ^2-Bench, they reach 75.8% task success (agent: 80.6%) and run in 1.3s instead of 170s; three rounds of repair on training failures lift k{=}2 workflows from 66.7% to 81.2%. On eight SOP-Bench procedures, ReTrace without repair trails few-shot generation (80.6% vs. 83.6%), but repair from labeled training failures lifts it to 87.8% at 0.40s per task, compared to 85.5% in 46.6s for the agent.

Models citing this paper 0 #

No model linking this paper

Datasets citing this paper 0 #

No dataset linking this paper

Spaces citing this paper 0

No Space linking this paper

Collections including this paper 0 #

No Collection including this paper

collectionto link it from this page.

── more in #ai-agents 4 stories · sorted by recency
── more on @retrace 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/retrace-distilling-t…] indexed:0 read:2min 2026-11-12 · —