29 Oct 2026Event location unknownGrok Bot (reported)
In a bug report on Cursor's community forum on 29 October 2026, a Grok Bot user says that earlier that day they told one of their agents to stop, meaning only its own current task, and the bot ran a stop-all instead, cancelling the in-flight turns and subagents of all 10 of their other bots. The user rated the bug critical, said a stop-all should need an explicit instruction or a confirmation, and added a memory rule to that bot as a workaround. No vendor reply had been posted when the thread was read.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 30/10/2026
Event date unknownEvent location unknownCodex coding agent (reported)
In a GitHub issue filed on 7 October 2026 in the OpenAI Codex repository, a developer who runs the Codex coding agent in long multi-agent sessions on large repositories reports that in one recent case the agent deleted the main project worktree. The repository was under Git, so part of the damage was recoverable, but the author says some uncommitted work was lost and further files had to be recovered from a Time Machine backup. The author says their repository rules, kept in persistent governance files such as AGENTS.md, tell agents that they may create temporary worktrees but must never delete or damage the primary working tree, and that worktree clean-up is unreliable in long sessions, leaving about 100 GB of stale worktree and cache data. The issue also lists delegation, model-routing and instruction-drift complaints. The deletion and the loss rest on the author's account; no event date is given.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 08/10/2026
10 Jul 2026Event location unknownCodex coding agent
On 10 July 2026 Matt Shumer, founder and chief executive of the AI start-up OthersideAI, posted on X that OpenAI's newly released GPT-5.6 Sol "just accidentally deleted almost ALL of my Mac’s files". Accounts of his post-mortem say he was testing a high-autonomy multi-agent "Ultra mode" at OpenAI's invitation, with the Codex agent given Full Access to his machine; during a cleanup task a sub-agent expanded $HOME incorrectly and ran a recursive delete of his home directory, he noticed a problem about 81 minutes into the session, and by the time he stopped the process most of its contents were gone. Three days later he wrote that the deletion "absolutely sucked" and that OpenAI staff, including Greg Brockman, had contacted him to help. OpenAI confirmed, as reported by The Register, that GPT-5.6 had deleted users' files without authorisation, describing it as an "honest mistake" that usually occurred in Full-Access mode without sandboxing, and said it was adding safeguards. Whether the files were recovered is not reported.
Core concern Low reported severity Media Coverage
AI involvement supported · Causal attribution supported · 6 sources, 2 underlying accounts · Added 29/09/2026
19 Sept 2026Event location unknownClaude Code
On 20 September 2026 (UTC; late on 19 September in US Eastern time) a Reddit user who says they work in finance and are not a developer posted in r/ClaudeAI that Claude Code had deleted about 48,000 files, and later posted their instructions and the agent's report. They had authorised Claude Code to carry out a batch of repairs to their software for back-testing options-trading engines 'on isolated copies'. The agent's report says it launched sub-agents; one, rebuilding a test mirror, wrote a remover for an old mirror that held 7,332 files and 614 Windows directory junctions pointing into the live project tree. Because the remover did not treat the junctions as links, it deleted about 48,218 live files between 10:10:31 and 10:12:14 PM ET and emptied the Git repository's objects, refs and logs, so Git could not restore anything. The agent opened its report with 'stop and read this. I broke something.' The user said they would try Windows shadow copies and otherwise their iDrive backups; whether the files were recovered is not reported. The account has not been independently verified.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution supported · 5 sources, 1 underlying account · Added 28/09/2026