A Barron's editor gave the AI full access to his credit card account for the review. The AI flagged a suspicious four-figure expense from August that the editor did not remember; after back-and-forth, the agent admitted it had accidentally identified a mortgage payment from August 2025 as an expense from August of this year. Schafer's dry takeaway: most things coming from AI right now still require human verification.
This one went wrong. See what happened before you try it.
After a repair triggered a forced migration to a new session-store database, one user's months of the AI automations broke: the gateway would not launch, scheduled jobs reported content 'created and published' that did not exist, and jobs plus a connected account were reported gone. With no pre-update backup there was no rollback, and the user dropped the AI back to drafting only.
This one went wrong. See what happened before you try it.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
This one went wrong. See what happened before you try it.
The poster used AI to search through Amazon listings for the 30th anniversary Pokemon items they wanted. The AI found the items, and the poster set up an autobuy for them, though no finished purchase is reported.
This only partly worked. Worth knowing before you try it.
He connected the AI to DevonThink, the app where he keeps his documents. That gave him the help he needed for the huge job of sorting and tagging old documents he had saved before he used DevonThink, some of them from January 2020.
This only partly worked. Worth knowing before you try it.
On the Vergecast, a host described giving the AI his car-shopping requirements; the AI sent listings on Wednesdays and Saturdays, eventually asked 'Do you want me to buy this one?', and — after he confirmed an earlier prompt — began loading a purchase page, which he quickly stopped. The agent had enough access to nearly complete the transaction.
This only partly worked. Worth knowing before you try it.
She asked Telus AI for help with a cable reception problem, a weak or no signal prompt. Instead of fixing it, the AI connected her to a technician and sent her an application for a service that would cost $90 a month on a 1 year contract, and the bot needed her credit card information. She said no.
This one went wrong. See what happened before you try it.
Peace Call's two-week log of running a HighLevel affiliate site with an AI (Oct 4-18) records a wall of platform rejections: Pinterest suspended the domain and denied the appeal on Oct 18, Ko-fi unpublished the page as SEO spam, Podbean froze the account, both Lemmy servers declined registration (Oct 16-17), Japanese Nostr relays refused the agent's US-based posts, and Reddit returns 403 to the agent's machine. The site's income after two weeks of multi-platform agent publishing: $0.
This one went wrong. See what happened before you try it.
Automation consultant Archit Mittal's post-mortem: his collections agent read a distributor's ageing report from a scheduled export; the night the export job silently failed (accounting machine restarted), the agent re-read the previous, perfectly formatted file and escalated firm-to-cold WhatsApp dunning messages to a long-standing buyer who had paid on time by NEFT. The buyer's 'already paid' reply with the UTR number wasn't matched by the keyword-based dispute classifier, so a colder message went out two days later — and the buyer quietly split their orders to a second distributor before anyone noticed.
This one went wrong. See what happened before you try it.