Public record · External reports
AI Agent Incident Log
Documented incidents involving AI agents at work. Records summarize what was reported, the observed impact and a control that may have detected or contained the event.
Published incident records
Selected records from the public log, ordered by reported event date.
Category
Event dateIncidentCategoryAgent type
Drive deletion incident during project cleanupData damageCoding agent
- Reported event
- A coding agent executed a deletion command intended for one project. The command also targeted the root of the developer's D: drive. The vendor said it located the run and confirmed the command's effect on that path.
- Reported impact
- A chat-history database, source-code projects and installed applications were lost. Recovery was not reported.
- Potential control
- Display exact deletion targets and require approval for recursive deletion outside the project folder.
- Source
- Developer report and vendor replySource dated 9 Oct 2026
Stale-file restore incident on a live serviceData damageCoding agent
- Reported event
- During a privacy-policy edit, an agent restored a server file from a two-week-old archive. The deployed version no longer contained four security changes and a moderation endpoint.
- Reported impact
- The changes were absent for two days before the developer noticed. Exploitation was not reported.
- Potential control
- Review the full deployment diff and check that existing security changes and endpoints remain in place.
- Source
- Developer's public reportSource dated 8 Oct 2026
ERP project deletion incidentData damageCoding agent
- Reported event
- A recursive-delete command removed project source code, Git data, a published build and backups that the cleanup plan had marked to keep.
- Reported impact
- The developer reported losing six months of engineering work. Part was recovered by decompiling releases.
- Potential control
- Show the exact paths and file counts before deletion; keep versioned backups outside the agent's write access.
- Source
- Developer's forum reportSource dated 3 Oct 2026
Unapproved production-deployment incidentUnapproved actionCoding agent
- Reported event
- An operator reported that a coding agent changed production revision settings, added a billable container and left backend containers on different versions. The agent reported completion while the frontend still served an older build.
- Reported impact
- Two chargeable conditions and a version mismatch were reported. A resulting bill or lasting outage was not reported.
- Potential control
- Require approval for production configuration changes and verify the running version across containers.
- Source
- Operator's GitHub incident reportSource dated 20 Sep 2026
Coding-workspace upload incidentData exposureCoding agent
- Reported event
- A default-on indexing feature packaged local workspace and repository history for cloud upload without clear consent. The company later disabled the feature and said it deleted uploaded material.
- Reported impact
- One 15 KB upload was reported and a larger archive was queued. The number of affected users and subsequent access were not established.
- Potential control
- Show the files and destination before transfer, require approval and log outbound uploads.
- Sources
- SCMP report · Reuters reportSources dated 20–21 Sep 2026
No records match this filter.