58% of tokens burned in failed agent runs happen after the model already had a clear signal to stop. Why is no one catching this mid-run?
Summary
A study finds that 58% of tokens consumed in failed AI agent runs occur after the model had a clear signal to stop, highlighting a missed opportunity for mid-run cost savings.
Similar Articles
The most expensive part of running AI agents isn't the tokens. It's the time figuring out why they did something.
Building AI agents reveals that the major cost is debugging—spending weeks chasing issues like upstream API changes—not just token or model inference costs.
Where agent systems quietly waste spend once they move past demos
The article discusses how AI agent systems waste spend in production due to hidden inefficiencies like over-context, inappropriate model selection, and retries, and questions what runtime decisions should govern model calls.
Your agent isn't failing because of the model, it's failing because nobody built a stop button
The article argues that the primary failure point for AI agents in production is not the model itself, but the lack of infrastructure such as stop buttons, billing oversight, and traceability for tool calls.
If your agent learned anything, why does Run 10 cost the same as Run 1?
Critique of AI agent token consumption; proposes Return on Token Investment (ROTI) as a metric for efficiency, noting that most agents do not reduce token usage over time.
Subagents Account for Most Token Costs in Long Agent Runs: Fixes That Cut Usage 70 to 90 Percent in Practice
The article analyzes a 2026 paper by Bai et al. showing that subagents and context bloat cause token costs in long agent runs to be ~1000x higher than chat, and presents three practical fixes (PLAN.md, read budget, out-of-band notes) that reduce token usage by 70-90%.