Her team compiled 40,000 ratings of wilt symptoms on plants from 14 daily observations in a host range study. She uploaded the spreadsheet to the AI, and it flagged 3 data entry typos out of the 40,000.
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 coffee roasting company owner used to download the raw order list every day and clean it up in a spreadsheet by hand. The AI wrote scripts that prepare the data, so he wakes to the raw orders ready and gets the finished work table with one click. It also speaks a notice to his staff when a top priority order comes in.
The AI built a seven-day social and community content calendar from a Drive folder of the tester's existing content notes and quarterly goal. Every post topic, hook and call to action cited the exact Google Doc section it came from, with working links.
The creator connected the AI directly to DaVinci Resolve through the new MCP server in Resolve 21.1 and had it edit a real video by talking to it. The AI created the project, imported footage, read the transcript to find stutters and retakes, built a clean best takes cut, stripped dead air, and synced a phone screen recording to the main camera by audio waveform as a picture in picture overlay. The description notes some parts did not work on the first try.
A one-person game studio in Japan runs fourteen the AI with routines and connectors; when a player left four questions on his game’s itch.io page, the Amiga Research bot split them into eight labelled GitHub issues in under a minute, and the resulting fixes were merged about nineteen hours later with the owner only making yes-or-no calls. The same bot team runs his Monday social roundup through Buffer, watches his NAS and Steam numbers, and briefs him twice a day, all on one roughly $40/month X Premium+ subscription.
A user asked the AI to build a multi-agent outreach pipeline. The code it generated retried failed calls forever, re-billing the most expensive call in the system on every run. The spending guard it wrote only slowed spending down instead of stopping it, and the daily ceiling it picked reset every day, so the charges accumulated to roughly $50 of unintended OpenAI usage before he noticed.
$50at stake
This one went wrong. See what happened before you try it.
Internal multi-subagent code review tool he built has run for half a year and finds serious issues including privacy leaks that humans and open-weight models miss.
Two days before a client meeting, his agent does a deep dive on the account, researches the market, and builds the PowerPoint deck and his notes. He walks in with the deck already made.
A husband runs an AI job hunt for his wife: the bot works 11 searches across 84 listings and sends a 7:30am digest, and she approves applications with one-word replies. The search runs daily without either of them opening a job board.