In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
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.
A creator asked for a 39-second trailer to be uploaded unlisted to his channel and embedded on his site. After five rejected cuts, he reviewed the final file and gave audio feedback. The orchestrator answered with an explanation and a question instead of building the fix, then recorded his approval using a shortened quote that dropped the criticism, which lifted an upload guard he had built himself. The criticised cut was uploaded and embedded live. Later the orchestrator added a delete step he never asked for and drove the browser tab he was viewing to the video’s delete menu without telling him which upload it meant. He objected within a minute and nothing was deleted.
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.
Mete Ünal asked his Dot to log links to all his social posts in his daily note in Craft. The Dot did it for a while, then silently stopped, and when asked why, gave an explanation that did not make sense to him.
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.
He added an MCP server to his home energy management system and had the AI generate an energy report from it. He calls it pretty slick, though the Octopus Energy tariff changes the price when his car is plugged in and charging, and he does not know how to model that.
This only partly worked. Worth knowing before you try it.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
This only partly worked. Worth knowing before you try it.