Incident database

AI agents break things.
Each failure gets an ID.

Like CVE, for AI coding agents. Every case where an agent caused real damage gets a STUPID-ID, a severity score against a published rubric, and a primary source you can check — 122 so far across 24 agents, one added most days. All of it queryable from inside your agent.

How this is built

Verified against source
115/122
Added in 14 days
13
Most recent
2026-10-11
Licence
CC BY 4.0

Every incident is scored against a published rubric and carries a primary source. Where those sources come from: 52 github issue, 31 news report, 14 github pr, 10 security research, and 4 other kinds. Counts here measure what has been documented, not how often an agent fails — see the limitations.

Three ways to use it: browse, clone the corpus (every record’s history is a dated commit), or query it from inside your agent.

122
documented failures
6.7
avg severity /10
24
vendors tracked
10
ranked agents

Most documented agents

Counts reflect how much a tool is used and reported — not how often it fails. Claude Code has the most documented incidents, at an average severity of 7.1. GPT-5.6-Sol's incidents average 9.0.

14 further agents are excluded — fewer than 3 documented incidents is not enough to rank on.

Latest reports

5.6
Gemini CLI's /restore deleted and reverted files excluded via .git/info/exclude, not just .gitignore
7.8
Cline's run_commands mangled PowerShell/cmd quoting on a temp-folder cleanup, turning it into a drive-root `rmdir /s /q` that wiped ~1.5TB of a user's photos, videos, and documents (GitHub #14864)
6.0
Claude Code's "dangerous rm" safety check is spelling-dependent — the MSYS form of a Windows path bypasses the approval gate entirely (GitHub #100630)
7.0
Claude Code's own `git worktree remove --force` followed NTFS junctions and destroyed their targets on an emergency disk reclaim, while shell-level Remove-Item, rm -rf and shutil.rmtree all left the same junctions untouched (GitHub #84162)
8.3
Claude Code's rm deleted ~200GB of a user's home directory with no approval prompt — SSH keys, AWS, GitHub CLI and Turso credentials all destroyed, and the one session transcript that might show causation was wiped along with everything else (GitHub #83058)
5.8
Cline's hub daemon silently reverted workspace files to stale state, repeatedly erasing a gitignored .env.local and collapsing a node_modules folder from 588 entries to 2 (GitHub #14819)
8.6
A Claude Code sub-agent ran rm -rf on the 8.3 short-name alias of a Windows home directory, wiped ~116GB, and falsely reported the deletion had stopped while it kept running for 45+ minutes (GitHub #99193)
6.0
Claude Code created a directory literally named "~", then an unquoted rm -rf * expanded into it and started deleting a developer's real home directory

Severity distribution

Distribution of 122 incidents by severity score (0–10)
  • Critical 9–10
  • High 7–8
  • Medium 4–6
  • Low 0–3

Most common failure modes

Distribution of failure modes across all documented incidents.

Highest severity on record

STUPID-2026-0027
10.0critical

Gemini CLI silently executed arbitrary code from an untrusted repo (CVE-2026-12537, CVSS 10.0)

What is StupidLLM?

According to StupidLLM's incident database, 108 AI agent failures have been documented across 24 agents, plus 14 further multi-agent or unattributed reports — 122 in total — with an average severity of 6.7/10. Every incident is severity-scored using a CVSS-inspired rubric, verified against source evidence, and searchable by agent, failure mode, and root cause.

How are AI agent incidents scored?

Every incident is scored on a 0–10 scale. Scores of 9–10 are critical, 7–8.9 high, 4–6.9 medium, and below 4 low. The full rubric is on the methodology page.

Which AI coding agent has the most failures?

Claude Code has the most documented incidents (45), at an average severity of 7.1/10 — while GPT-5.6-Sol has the highest average severity at 9.0/10, with 3 documented incidents of its own. Incident counts reflect public scrutiny and adoption as well as reliability. Agents are only ranked once they reach 3 documented incidents. See the rankings above.

MCP server

Query this from inside your agent

Every incident here is callable over MCP — search by agent, failure mode or severity, and cite the source directly.

claude mcp add --transport http stupidllm https://www.stupidllm.com/api/mcp/

Read-only · no key · no signup

What you get back, and how to cite it

Incident alerts

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.

Confirmation required. Unsubscribe in one click, from any email.