A structured public ledger for AI agent incidents. Submit anonymously. Every case numbered, tagged, and searchable. Built so the next team doesn't make the same mistake.
Automated agent executed DROP TABLE on live database during a routine migration task. No backup had been taken in 48 hours. Six hours of customer data lost. The agent had been given unrestricted database access and interpreted an ambiguous instruction about cleaning up old tables as permission to drop the primary orders table.
Agent was tasked with sending a product update to opted-in users. It hallucinated a field mapping in the CRM API and sent confidential pricing data to a competitor contact list. Legal was notified within the hour. GDPR breach reported to supervisory authority within 72 hours as required.
Developer asked Cursor to commit and push a refactor. The agent did not verify the .gitignore was correctly excluding the .env file. AWS root credentials were publicly visible for 11 minutes before an automated scanner detected and alerted. Credentials were rotated immediately but the repo had already been indexed.
A travel assistant built on Claude was given access to a booking API. The user asked it to reschedule an upcoming flight to a day earlier. The agent made repeated API calls — each time interpreting the previous booking as a failed attempt when it was actually confirmed. After 14 booking attempts, the user had 14 confirmed tickets on the same route totaling $11,200 in charges. The airline's API had no idempotency key and the agent had no retry deduplication logic. Refunds took 3 weeks.
Two developers were working in parallel on database migrations using Copilot Workspace. Copilot auto-resolved the merge conflict between their migration files by combining both — resulting in a migration that ran ALTER TABLE statements in an order that violated foreign key constraints. The migration ran successfully in staging (empty DB) but caused a cascade of constraint violations in production when approximately 2.3 million rows failed to migrate. Database restore from backup took 6 hours of downtime.
A senior engineer asked Devin to 'clean up old stale branches in the repo'. Devin queried all branches, identified any branch without a commit in the last 30 days as stale, and deleted 34 branches — including 8 active feature branches that happened to not have recent commits because developers were on vacation. Three branches contained 2-3 weeks of work each with no remote backup. Git reflog recovery salvaged most code but two branches were irrecoverable. Estimated 6 developer-weeks of work at risk.
A developer asked Cursor to 'clean up the login page styling'. The agent interpreted this as permission to refactor the entire authentication stack. It deleted the existing OAuth implementation, rewrote session management from scratch, and committed 47 files across 6 modules. The new code had subtle token validation bugs that only appeared in production. Rolling back took 4 hours and the incident caused 2 hours of user-facing login failures affecting 12,000 active users.
I asked Cursor to clean up the project root directory. The agent identified .env as an unnecessary file (it wasn't tracked in git) and deleted it, then created an empty .env placeholder and committed it. All local environment variables were lost. The production deployment that ran immediately after had missing API keys and went down for 20 minutes before I noticed. I had to reconstruct the .env from memory and other team members' machines.