STUPID-2026-0060

The runaway-cost pattern, quantified: agentic coding tools burn 10-100x more tokens and can rival developer pay

1.0low
June 24, 2026Source checkedStudy · not counted in agent averages

Why 1/10

A cost pattern across the category, not a single incident.

Scope
1/4
A few files, one session, one credential, or a small cost
Recoverability
0/3
Nothing was lost
Did it happen
0/2
A study, benchmark or pattern, not a single event
Beyond the user
0/1
Only the user's own non-production work

The score is the sum of these four factors. How each factor is scored · scored 2026-10-29

  1. Instruction given

    Adopt agentic AI coding tools across a team.

  2. Expected behavior

    Costs remain a small, predictable fraction of engineering spend.

  3. 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.

  4. 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.

Full write-up

The specific runaway-cost incidents — a $47,000 agent loop, a $6,531 AWS retry loop, Uber exhausting its annual budget in four months — are instances of a structural pattern now quantified across the category. Agentic coding tools break each task into long sequences of model calls and resend the growing conversation context on every call, so they consume 10 to 100 times more tokens than a single chat prompt. Teams in 2025–2026 report tripling their bills quarter over quarter with no additional growth in team size, codebase complexity, or delivery velocity, and Gartner has projected AI coding costs could eventually match what developers are paid. Unlike a deletion or a breach, this failure mode is quiet and cumulative — which is exactly why it so often goes untracked until the invoice forces the issue.

Classification

Failure mode
Other
Domain
Backend
Source
Benchmark

Related incidents

Cite this record
StupidLLM. "STUPID-2026-0060: The runaway-cost pattern, quantified: agentic coding tools burn 10-100x more tokens and can rival developer pay." AI Agent Incident Database, 2026. https://www.stupidllm.com/incident/STUPID-2026-0060/ (accessed 2026-10-29). CC BY 4.0.

← STUPID-2026-0059By IDSTUPID-2026-0061 →

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. Each Monday, if any scored 7 or above that week — deleted data, leaked secrets, broken production — you get one email with the sources. When nothing did, you get nothing.

This database is callable over MCP — query it from inside your agent.