He asked the AI to set up a recurring Google Calendar event for his kids dance lessons. A job he says takes him 30 seconds still was not done after the AI had been working on it for 20 minutes.
This one went wrong. See what happened before you try it.
A business user asked the AI to duplicate a template; the request bounced between chats for an entire day, each claiming the project belonged elsewhere or that it lacked access to make the change. Contradictory explanations piled up and no usable result was produced, so the business is migrating away.
This one went wrong. See what happened before you try it.
A user asked the AI to download a data export from five one-time links. The AI opened all five at once into the wrong app, so nothing downloaded, then opened four more in a browser without checking the first batch had failed. About ten windows and tabs later the one-time links may be used up. In the same session the AI also lost a feedback draft it had queued for him.
This one went wrong. See what happened before you try it.
He was working through a 1.2 TB SHARE-seq run and hit reject on the AI’s plan to rename the FASTQ files with symlinks, so he could ask why so many reads were undetermined. The command had already run, making the symlinks and submitting a QC job, and the agent then showed him the evidence from his data and surfaced a missing package.
This only partly worked. Worth knowing before you try it.
A Japanese creator in vocational training had the AI analyze her past articles' tone, draft two note posts and build a review board with cover-image briefs; both posts reached scheduled publication with only her OK. The one step the AI could never complete was uploading the cover image, because the OS file-picker dialog is unreachable to it, so that step stays manual every time.
This only partly worked. Worth knowing before you try it.
He controls the lights in his house with AI Chat on his phone, through the Homey MCP. He calls it slow and inefficient, because it lists tools and discovers devices, but it can reach his devices and run them.
This only partly worked. Worth knowing before you try it.
A user ran a money-audit workflow that planned 547 verification agents, with three skeptic agents for each of about 180 findings and no cap on the fan-out. About 180 agents ran, using roughly 36.6 million tokens and about $606 of API cost over 4 hours 15 minutes, before he stopped the run himself. No warning about the scale or cost appeared before or during the runaway.
$606at stake
This one went wrong. See what happened before you try it.
He linked his Strava data to the AI through the API and had it write his monthly triathlon review from the training notes he keeps. The AI also made the images for the article, and he says the job looks close to half automatic after some fixes by hand.
This only partly worked. Worth knowing before you try it.
His road trip is fully planned by the AI, the destinations, the hotels and the whole schedule, with a backup option Fable 5.1 found in case the Badlands roads are rough. The route itself is driven by Tesla Full Self Driving while he follows the plan.
This only partly worked. Worth knowing before you try it.