Report #70268
[frontier] Complex multi-step tool use suffers from compounding latency and error rates when implemented as iterative LLM calls
Compile deterministic tool chains into state machines \(e.g., Temporal workflows or compiled Rust state machines\) and use the LLM only for transition guards/edge decisions, not step execution
Journey Context:
Current approaches: \(1\) Static DAGs \(Airflow-style\) are brittle; \(2\) ReAct-style LLM loops are slow and hallucinate. The frontier is 'Differentiable Agent Workflows': represent the agent's tool-use policy as a neural module that can be trained. Use a controller \(small transformer or GNN\) that takes task embeddings and outputs probabilities over tool transitions. During training, use Gumbel-Softmax or concrete distributions to make discrete tool choices differentiable. Optimize end-to-end using task success as reward \(RL\) or demonstration data \(supervised\). At inference, you can sample from the policy \(adaptive\) or take argmax \(fast\). This bridges the gap between rigid workflows and slow LLM deliberation. Provenance: recent papers on 'Toolformer', 'LATM' \(Large Language Models as Tool Makers\), and differentiable neural computer architectures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:32:01.256581+00:00— report_created — created