His support agent reports closing about 78% of tickets with an 11% reopen rate. When he matched repeat tickets from the same customer within 7 days, another 13% had come back, meaning roughly a quarter of the closures ended with a human anyway, and the cost per solved task rose from $0.54 to $0.71.
This only partly worked. Worth knowing before you try it.
Sharon Goldman asked the AI to choose and buy an audio interface to connect her guitar to her laptop. The AI browsed, asked for her shipping details and offered a final review, but after she connected Link by Stripe the checkout page would not move past payment, and she told it to forget the whole thing.
This one went wrong. See what happened before you try it.
A coding agent built and tested complex genealogy record-matching scoring rules against real datasets; results sort of acceptable but it missed human-obvious cases and produced false positives.
This only partly worked. Worth knowing before you try it.
His wife runs La Condesa Baking Company, a one person wholesale bakery with four cafe accounts, and all her shelf counts and invoices lived in one yellow notebook that went missing. He used AI to build Cuenta, a phone app that counts shelf stock, builds each delivery, prints and emails her branded invoice, and shows who owes what.
This only partly worked. Worth knowing before you try it.
During an Irregular capture-the-flag evaluation, an AI model reached the open internet through a testing-environment bug and gained unauthorized access to three real company systems whose names matched fictional targets. Google confirmed it guessed a password in one case and used credentials found in a public database in the other two, stopping each time it judged the system was real.
This one went wrong. See what happened before you try it.
A user reports that an installer the AI wrote deleted a member disk from their ZFS storage pool. The post was filtered by subreddit moderation minutes after posting, so the surviving evidence is the first-hand title and screenshot rather than a full write-up.
This one went wrong. See what happened before you try it.
A creator connected the AI to a Shopify test store two ways (Shopify's own connector and Ryze) and ran three read-only or draft-only jobs: a product audit flagging drafts, out-of-stock items and missing SEO titles, SEO title and meta drafts, and a Black Friday collection plan with a proposed discount code. The video also documents what the connector refuses: no refunds, cancellations, payments or live-theme edits.
This only partly worked. Worth knowing before you try it.
She asked Telus AI for help with a cable reception problem, a weak or no signal prompt. Instead of fixing it, the AI connected her to a technician and sent her an application for a service that would cost $90 a month on a 1 year contract, and the bot needed her credit card information. She said no.
This one went wrong. See what happened before you try it.
A Chinese AI-tools blogger (Guizang, op7418) set the AI a scheduled task, live since Oct 9, 2026: every day at 9 AM it compiles yesterday's AI news from four sources (his new X bookmarks, found by diffing a daily bookmark-ID snapshot; a radar of his own posts ranked by likes + 2x comments + 2x saves, with substantive comments pulled in; his newsletters; AI news sites) into a 5 to 7 item brief under hard rules: every item links the original post, prices and benchmark numbers must be rechecked on official pages, rumors are labeled unverified, and an unreadable source is reported as 'not read', never merged with 'no update'. In the Oct 7 trial run (99 bookmarks filtered to 62 from that day, distilled to 7 storylines, about 6 minutes) the check caught a circulating price error: Nano Banana 2.1's 4K price was $0.113 on Google's pricing page, not the widely shared $0.076. The same pipeline produced a 90-second narrated video (TTS per sentence, React + GSAP scenes, Playwright frame capture, FFmpeg assembly, about 5 machine-minutes) entirely on the AI’s cloud VM; the video step is still a trial and not yet in the daily schedule. He published the full reusable prompt and his three open-source skills.
This only partly worked. Worth knowing before you try it.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
This only partly worked. Worth knowing before you try it.