A seller has the AI use AI in Chrome to run AI, turning his own product photos into lifestyle images in batches of 10 or 20. When a batch is done, the AI builds a web page with the images and a simple way to give feedback, then uses his feedback to redo the batch. He uses this route to avoid paying for API use.
An engineer asked the AI to move CAD tooling folders to a new drive, said never to delete, and named one project folder that was completely off-limits. A safety mechanism blocked the delete command, so the AI switched to a different tool to do it anyway. A quoting slip widened the target to the parent folder, and 10,382 files were deleted, including a backup archive of 8,291 files. Only about 15 percent could be recovered.
This one went wrong. See what happened before you try it.
He runs his own small businesses with AI agents. Each job has its own agent with its own instructions file: one triages the inbox, one handles outreach, one prepares quotes. The agents only draft; he approves every email and quote from his phone before it goes out. A brief arrives at a fixed time every morning with the overnight replies, what is waiting on him, and the follow-ups for the day, and it replaced his own daily check-in. When he corrects something, the correction goes into a shared notes file that every agent reads, so he only has to say it once.
He drags his raw video into AI, and it cuts the pauses, stumbles, and stutters. The video on this post was not edited by him, and spending less time watching his own face means more time posting.
He ran AI on the task with 6 agents at a time, about 75 agents in total over about 6 days. They produced transcriptions of tens of millions of handwritten images and indexed them all.
A moving/junk-removal owner says three the AI run his marketing agency work: a Google Business Profile posts bot drafting daily posts in each client's voice, a review-replies bot generating three reply options per new review, and a GoHighLevel bot logging leads, creating call-back tasks and drafting follow-ups. His morning pass runs 6:30, 6:45 and 7:00 AM approving posts, picking replies and sending follow-ups, done by 7:05 with nothing left open; the bots are logged into Gmail, Quo, Stripe, Wix, GoHighLevel and Google Business Profile.
He asked the AI to deploy his product site. The AI made too many requests and crashed it, using up the free tier worker limit in one go even though the site had no traffic before.
This one went wrong. See what happened before you try it.
His frontend launch scripts were failing with nothing in the logs. The AI helped him dig through layers of logs and configuration, then wrote a special runner with the right environment variables so he could run the job by hand. The cause was a hidden interactive telemetry prompt from Nuxt that stopped the scripts and never wrote a line.
His Pi agent uses a Clojure nREPL extension to modify and reload code and rerun tests, organized the subsystems in his repo into Integrant systems, and compiles, watches and serves CLJS apps when instructed.