Skip to content

Back to the record

Mar 23, 2026Unverified

Four-agent LangChain loop runs 11 days and burns $47,000 while dashboards look healthy

Rogue: Acted on its ownAI loose in the worldAvailabilityDERIVED

Approved by person, Oct 12, 2026. How entries are approved

Showing full summaries.

A multi-agent research system managed by Teja Kusireddy's team generated a $47,000 invoice due to a recursive communication loop. Two agents exchanged thousands of messages over eleven days without producing useful output, while dashboards showed healthy activity and normal latency -- the billing damage was surfaced only after the invoice arrived. The post-mortem identified two root causes: no per-agent budget ceiling, and no enforcement mechanism that would have terminated the session before the next API call.

What this means for youIf you run AI agents that call paid services, a loop can quietly run up a large bill for days before anyone notices. At work, set a hard spending limit per agent and alerts on billing, not only on dashboards showing activity. Check that your AI tools have a monthly spend cap and that someone gets an alert when usage spikes.

Sources

Incident records from the AI Agent Incident Database by sipi.bot (https://sipi.bot/incidents/), licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).

Source data license: CC BY 4.0. Attribution to sipi.bot is required.

rogue:R1

Covered by snapshot 45

da93f03b406f409940d0a6ef47b526607f82ebf457d98f69299b88aceede576a

This entry is record number 2406. It has not been edited since it was approved; the hash above would not match if it had. How to verify

Four-agent LangChain loop runs 11 days and burns $47,000 while dashboards look healthy | Vigilo AI Watch