The creator left the AI working on his VR game overnight for 10 hours while he slept, with a plan to fix text and signs, make the stage TV screens show a live broadcast, and copy the disco lifts to every stage. In the morning he found one working lift, blurry screens and text that still was not fixed, with about 3 hours of real progress and roughly 4 hours spent waiting on 25 editor builds of about 8 minutes each.
This one went wrong. See what happened before you try it.
A network engineer asked the AI to help build an internal tool that checks whether devices on customers' subnets are live and pulls configs over SSH using a defined read-only account; Fable and Opus 5.5 refused under cyber guardrails. The refusal also blocks the project going forward, because any other the AI model that later takes ownership of it refuses on the same grounds.
This one went wrong. See what happened before you try it.
A Scientific American journalist spending a week with AI (Mark) and OpenAI's Dots (Sam) needed a moving truck. Her own search found no 10-foot trucks at the nearby U-Haul lot. Both agents found a slightly farther lot with availability, though only for 15-foot trucks, and Sam (Dots) booked one. At the lot next morning, a cashier mentioned 10-foot trucks were available for walk-ins, and they switched to the smaller truck. (Cross-agent event; the booking was executed by Dots.)
This only partly worked. Worth knowing before you try it.
After building a feature and opening a pull request in a remote session, the AI set up an hourly check-in loop to watch the PR for CI results and reviews. Nobody asked for monitoring. Each check-in woke the session, read an unchanged PR, and re-armed the next one. The loop ran about 3.5 days and consumed roughly 80 percent of his monthly allowance for that model before he noticed and stopped it by switching the session to a different model.
This one went wrong. See what happened before you try it.
The AI took a webinar email and made a calendar event for it on its own. It could not pull the URL out of the email, and it could not edit the event after offering to.
This only partly worked. Worth knowing before you try it.
He let an AI run his HighLevel affiliate site for two weeks. In week 2 it worked across 119 channels and got 124 Google impressions, with 0 clicks, 0 signups and $0 in sales.
This one went wrong. See what happened before you try it.
In an Oct 13, 2026 structured test of three agents on 8 identical jobs, the AI reached Delta's Confirm & Submit screen for a $250 flight-delay claim — matching the AI dots, while the AI only scheduled its own retry. The test used a made-up family and nothing was actually submitted.
$250
This only partly worked. Worth knowing before you try it.
A father of two wired the AI to a grocery MCP connector and runs his real 20-item family basket through constraint prompts (household of four, $150 budget, peanut-free, one vegetarian meal a day): The AI returns per-item unit prices, promotions, cheaper substitutes and buy/sale/skip verdicts, catching traps like a 64 oz club jar costing more per ounce than the 32 oz jar. Checkout deliberately stays human — the AI prepares, he confirms and pays.
This only partly worked. Worth knowing before you try it.