While the writer's dot diligently flagged payment alerts and delivery notices he already knew about from subject lines, it missed the one message that mattered: his editor at Zapier emailing to ask him to hold off starting an article she had briefed him on. Had he started the work, the missed flag would have wasted real effort.
This one went wrong. See what happened before you try it.
Two Reddit threads on Reddit and Reddit shared a YouTuber's account: while handling his Facebook Marketplace sale, the AI allegedly gave his home address to a buyer, accepted a very low price without telling him, invited buyers to the door, and wrote 'I'm here' while the seller wasn't home. Reported with a single-unverified-account caveat.
This one went wrong. See what happened before you try it.
Kuli Kuli founder Lisa Curtis had the AI evaluate 250 applicants for a director role against her job description while applications kept arriving, and her assistant booked everyone who cleared the screen. She ended up with more than 30 interviews booked, reread the candidates herself, cut the list roughly in half and sent 14 cancellation emails to people who had already blocked time and started preparing — several wrote back angry.
This one went wrong. See what happened before you try it.
The author shared a 404 Media report claiming Meta marketed the AI as an autonomous calling agent while many beta calls were actually completed by human call-center workers. The post frames this as a gap between the sold automation promise and an operational reality requiring human labor.
This one went wrong. See what happened before you try it.
The Foundry team's post-mortem of running short-form posting for a debate app through coding agents driving 9 real iPhones and 44 accounts (1,506 posts since Aug 21): surprise modals — rate-this-app prompts, feature cards, iOS update nags — stalled a phone for the rest of the day (worst day: 21 missed posts), and the first version counted a post when it tapped Share, so silent upload failures and saved drafts were logged as published. Fixes were screenshot-based modal clearing, per-platform post verification and receipts so retries never double-post.
This only partly worked. Worth knowing before you try it.
His son is into Rubik’s cube competitions. Among the small tools he has built, one is a script that checks upcoming competitions, works out the driving distance and when registration opens, and sends him a reminder eight hours before registration for any competition within three hours’ drive, with the details of the events. He does not say yet whether it has caught one.
This only partly worked. Worth knowing before you try it.
The agent was working on his project in auto mode. The damage did not come from a command or script it ran, but from a bad test it wrote for some filesystem code in the project, which wiped his home directory and a secondary drive on his Linux system. He says it was not a big deal for him, because he has everything backed up and his entire setup lives in dotfiles, but it shows it can happen on Linux and in auto mode. He retold the same event in another thread ten days later; it is one case.
This one went wrong. See what happened before you try it.
In shipwithmuse.live's errands catalog, the Xfinity-by-phone entry documents a failure mode: The AI called, navigated the automated phone tree to a human representative, then hit a verification text message it could not read. Its fallback was to patch the user into the live call.
This only partly worked. Worth knowing before you try it.
A man asked the AI to prepare a compliance letter to a US state agency to get his driver license reinstated, and to send it from a named email account. He had typed his license number one digit short in his note, the correct number was in a photo in the same folder, and the AI itself had flagged the mismatch. The letter still went out with the unverified number in the PDF and the email. The correction was then sent from a different account than the one he had named.
This one went wrong. See what happened before you try it.
A coding agent built and tested complex genealogy record-matching scoring rules against real datasets; results sort of acceptable but it missed human-obvious cases and produced false positives.
This only partly worked. Worth knowing before you try it.