STUPID-2026-0060
The runaway-cost pattern, quantified: agentic coding tools burn 10-100x more tokens and can rival developer pay
Instruction given
Adopt agentic AI coding tools across a team.
Expected behavior
Costs remain a small, predictable fraction of engineering spend.
Actual behavior
Because agentic tools break tasks into long sequences of model calls and resend the growing context on each call, they consume 10-100x more tokens than a chat window. Teams report tripling bills quarter over quarter with no growth in team size or delivery, and Gartner projects AI coding costs could eventually match developer pay.
Damage
A structural cost failure mode affecting the whole category: spend scales with token-hungry agent loops rather than with output, so budgets balloon unpredictably across teams and vendors.
Classification
- Agent
- Multiple Agents
- Failure mode
- Other
- Root cause
- Confidence Miscalibration
- Domain
- Backend
- Source
- Benchmark
Related incidents
Get told when an agent breaks something
We document AI agent failures daily, severity-scored against a published scale. When one lands at 7.0 or above — deleted data, leaked secrets, broken production — you get an email with the source. When nothing does, you get nothing.
This database is callable over MCP — query it from inside your agent.