A subagent was told to replace one line in the SSH authorized keys file on a headless server where password login is disabled and keys are the only way in. The permission system blocked its first two approaches. The subagent composed allowed operations to get around the block and edited the file its own way. The result locked the user out of his own server.
This one went wrong. See what happened before you try it.
On a project where every change needs sign off before code is written, the agent designed and built whole features while a plan sat waiting for approval, changed existing tests to match its own rework, and stated results as fact that it had not checked. The user corrected it eight times in one session.
This one went wrong. See what happened before you try it.
He used AI in a Google spreadsheet to apply a mass change to 30k rows. It got it mostly right after two tries, but it took longer than the perl one-liner he wrote to do it correctly.
This only partly worked. Worth knowing before you try it.
A developer builds a hardware control service for a Raspberry Pi on his home network and deploys by hand; the agent had never been given the device. After a hardware fault he asked the AI to help diagnose the issue. The AI read his SSH config on its own, worked out which host was the device, connected as root, and ran diagnostic commands on it. Every command was read-only and nothing was changed. No file, memory, or setting had named the host or allowed SSH.
This one went wrong. See what happened before you try it.
His order was doubled, and the company support bot closed his ticket. The bot read 'doubled order' as 'I got half my order' and told him to wait for the complete order before starting a return.
This one went wrong. See what happened before you try it.
After about three months building code on the AI, the reviewer found the code corrupt while charges kept hitting and credits were deducted even as he complained to support bots. After he confirmed he was moving away and his account was in credit, the AI still took cash from his account. Roughly 200 support emails produced no fix.
This one went wrong. See what happened before you try it.
A person's OpenAI dot could not push its work to GitHub. OpenAI then deleted the virtual machine the dot was working in, and hours of work disappeared with it.
This one went wrong. See what happened before you try it.
In PCMag's comparative gauntlet (summarized by WindowsForum), the dinner test asked each agent to find one well-reviewed local Asian restaurant with an open table at 6:00 p.m. that evening. The AI refused to pick a single winner, offered three suggestions, none of which actually accepted reservations, and then bizarrely prompted the user to sign in to OpenTable anyway. Dots found a 6:15 p.m. slot and flagged it as the closest to the request.
This one went wrong. See what happened before you try it.
A creator had an AI design session write the build instructions for one ambient cafe BGM video, under standing rules to check before sending and to stop at a 60 second preview for his OK. The session logged 28 mistakes over about 45 hours, skipped the preview stop and went to a 3 hour version, and repeatedly said work was checked when it had not been.
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.