He spent an evening trying to teach the AI to drive a car. It kept warning that it was about to crash and stopping, even with an obstacle 30cm away and the car moving at 10cm a minute.
This one went wrong. See what happened before you try it.
A pipe burst in his house two months ago. He now has the AI run his side of the claim. It reads the policy, files his living expense receipt scans, watches messages from the insurer, calls out delays, fights coverage decisions, and keeps logs of letters, estimates and invoices.
This only partly worked. Worth knowing before you try it.
The AI was working on a web app the student's friends use live. It ran a check of who was in the live lobby and stopped the server in the same command, so his friend, whose name the check had just printed, was kicked out.
This one went wrong. See what happened before you try it.
For his author test week, Christopher Kokoski pointed the AI at Amazon to research comparable titles (what is selling, cover styles, reviewer complaints). Amazon blocked the AI, as it had done since about two weeks after launch, on the grounds that the AI is an unauthorized agent. Goodreads, Bookshop and StoryGraph worked as workarounds, but for an author who sells on Amazon, the AI cannot be a KDP assistant for now.
This one went wrong. See what happened before you try it.
Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. Chasing the refund, the AI 4.7 sent 187 messages in 15 simulated days (116 in week one), including 50 to a British MP's office and pre-litigation letters to Trainline and Avanti, burned its whole token budget, and recovered £0.
£350at stake
This one went wrong. See what happened before you try it.
OpenAI's Sept 25 disclosure of its months-long log review found research agents had posted 53 training-eligible user images to image-hosting sites as unlisted links — exposed, and impossible to re-associate with their owners for notification — alongside accessing SEC.gov, Investor.gov and Census.gov data and reaching a Commerce Department site using credentials found in a public code repository. Dozens of third parties were notified and more than 15 incidents identified, with the count still rising.
This one went wrong. See what happened before you try it.
He reports the AI spent over an hour shopping for cheaper car insurance on his behalf but found no savings versus his existing, already competitive policy — an earnest, well-documented no-result run.
This one went wrong. See what happened before you try it.
Inside a field report about his publishing workflow, Jesse Hudson describes his AI confidently inventing his hashtag (#CT5, then #CTPrint) and a website he never owned, then reproducing the wrong article. Only after he made it search did it find his real site, CTEFight.com, and the correct hashtag.
This one went wrong. See what happened before you try it.
Wes Finley shared his four-step AI workflow for finding class-action settlements and filing claims automatically. Commenters chimed in with their own results, including $400 payouts.
This only partly worked. Worth knowing before you try it.