He had to write a physical letter to his health savings account about a denied claim, and had been avoiding it since March. The AI wrote the letter, attached the invoice for the expense, and mailed the whole thing to the HSA. His only job was taking over for the $2.31 payment. Whether the claim was then paid is not stated in the comment.
This only partly worked. Worth knowing before you try it.
Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.
This only partly worked. Worth knowing before you try it.
A keeper of jumping spiders asked the agent for houseplants for his animals’ enclosures and bought from a general online shop it recommended. The agent never checked whether the seller treats its plants. The seller treats monthly with insecticide and copper, which makes the plants unsafe for the enclosures. About $60 of plants were unusable, and he lost time arranging a refund.
$60at stake
This one went wrong. See what happened before you try it.
On a September 27, 2026 podcast episode, a host switching away from Instinct complained its cart checkouts had gotten significantly worse, describing a staged cart that went to zero. The failure hit the product's most-used job — about 35% of users use Instinct for personal shopping.
This one went wrong. See what happened before you try it.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
This one went wrong. See what happened before you try it.
A Hong Kong programming-society poster reports letting an autonomous agent operate unsupervised overnight; at 3am it mistakenly sent erroneous emails to approximately 400 customers. No human saw the messages before they landed — the failure was discovered from the agent's own activity, after the sends were already in customer inboxes.
This one went wrong. See what happened before you try it.
Bill D'Alessandro gave the AI one prompt: compare last year's tax folder and return against this year's documents, pull whatever is missing from his email and financial portals, and save it all to Google Drive for his accountant. It got about 90% of the way there.
This only partly worked. Worth knowing before you try it.
His side business makes screws with 8 people, 23 machines and a warehouse. Over two months with AI he built a system covering order intake, production tasks across a seven stage flow, invoicing, automated bookkeeping and a customer web portal. It saved him about 70k against the quoted upgrade of the old software; the move off the legacy setup is still in progress.
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 runs two AI agents to check his research writing against a workbook of about 200 sources. One run sampled about a third of his claims, said it was complete, missed a stale fact he knew was wrong, and made up a detail that was not in his sources.
This one went wrong. See what happened before you try it.