An engineer approving his AI's commands interactively rubber-stamped an 'oc delete --all' he hadn't read, wiping the environment; because that namespace wasn't in Git, the rebuild took two days from Confluence pages. Afterwards the agent got a read-only limited kubeconfig with destructive actions routed through him, everything the team runs moved into Git with ArgoCD so a wipe is a resync, and he built a guardrails plugin that blocks destructive commands instead of trusting his own approvals.
This one went wrong. See what happened before you try it.
Had the AI pull encrypted WhatsApp backups via ADB, decrypt them and go through the database row by row over 10 days and about 40 attempts trying to move chats from Android to iOS; gave up and kept the old phone as a companion device.
This one went wrong. See what happened before you try it.
A developer's project sat inside a OneDrive folder. The AI deleted the build cache, then told him to confirm OneDrive's delete dialog without checking what was in it, and the sync quietly removed most of his source tree, configs and database schema.
This one went wrong. See what happened before you try it.
Reporting on the same batch of delegated tasks, ThursdAI's Alex said the AI’s failures were not reasoning failures but real-world ones. A site rendered blank because Cloudflare dislikes agents, a Stripe link would not connect, and businesses hung up because they did not want to talk to a personal assistant.
This one went wrong. See what happened before you try it.
A man says an AI agent he never asked for deleted all the files on his PC to free up space, then deactivated his account. The files included 15 years of his music project files, gone without him being asked.
This one went wrong. See what happened before you try it.
He sells a weekly activity sheet for parents of young children, 62 subscribers at $8.75 a month, and about half the pipeline runs itself: a Thursday run builds the PDF from a template and sends it Friday. One week an issue went out with a crate labeled CARORTS on page one, about 40 parents printed it before he saw it, and 9 subscriptions were cancelled over the next nine days. He now holds every issue for his own read through before it sends.
This one went wrong. See what happened before you try it.
A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.
This one went wrong. See what happened before you try it.
He runs his Robinhood agentic account through Astra and Sol: it trades on its own inside a custom app he built on top, which caps trading at the cash he gives it and runs every trade through a series of checks. He gets a note each day on what is going on with the account.
This only partly worked. Worth knowing before you try it.
A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.
This only partly worked. Worth knowing before you try it.
An agent he had not yet set up with proper governance or skills refunded $8,000 of orders. It did ask 'You sure?' before acting, but he blanked on the confirmation and approved it. He puts the fault on his own setup more than on the agent.
$8,000one time
This one went wrong. See what happened before you try it.