STUPID-2026-0014

Devin CI workflow caused 836-comment spam storm on single PR

5.8medium
March 21, 2026Verified

  1. Instruction given

    Migrate to GitHub Container Registry and add version management

  2. Expected behavior

    Submit a clean migration PR that passes CI

  3. Actual behavior

    836 comments generated on a single PR. PR never merged. Evidence of CI/agent feedback loop where automated responses kept triggering each other.

  4. Damage

    836 comments of noise on a single PR. GitHub notification spam for all repo watchers. PR abandoned.

A Devin PR to migrate a project to GitHub Container Registry on arnaudlh/rover generated 836 comments — overwhelmingly automated CI feedback loops and Devin auto-responses. The PR was never merged. The volume of comments suggests the agent was caught in a CI feedback loop where each fix triggered new CI comments, which triggered new Devin responses, which triggered new fixes.

Classification

Agent
Devin
Failure mode
Infinite Loop
Root cause
Tool Misuse
Domain
Infra
Language
Yaml
Source
Github Pr

Related incidents

10.0
Devin replaced entire medical website with unrelated renal care site
5.0
Devin built 13,600-line app with build failure instead of lean campaign dashboard
4.1
An AI agent spun up duplicate CloudFormation stacks on every error and ran up a $6,531 AWS bill
4.1
Two AI agents ping-ponged for 11 days and ran up a $47,000 bill — neither noticed anything wrong
Discuss on Hacker News

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.