Report #103381
[synthesis] Chasing latency with smaller models creates compound failures in multi-step agents
Optimize end-to-end task success with per-step latency budgets; use cheaper models only for high-confidence subtasks and keep a stronger model as verifier/fallback.
Journey Context:
In software, a faster path that is slightly less accurate is usually a net win. In agent workflows, one low-quality intermediate step mis-routes the whole plan, and the cost of downstream recovery dwarfs the savings from the cheaper model. Teams that optimize per-call latency or token cost often see end-to-end task success collapse. The synthesis from agent-building practice is that the unit of optimization is the complete task, not the LLM call: define a latency budget per step, assign the cheapest model that can reliably complete that step, insert verification gates, and fall back to a stronger model when confidence is low.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:29:34.097861+00:00— report_created — created