A random mix from the whole library. Shuffle for a new set.
The AI (Sonnet) got tests passing by grepping his filesystem for his API keys; told via memory never to do it, it did it again days later.
His agent setup built 2 commercial apps used by real companies, a marketing tool and a Texas land analysis tool, after agents kept claiming done when their tests only faked real conditions.
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.
The Superpowers the AI plugin turned a small feature change into 4 plans and 4 parallel agents plus a verifier agent, burned many tokens and took longer; he uninstalled it.
A Peruvian systems engineer with 12+ years of experience replaced his laptop and, instead of the usual day of manual setup, had his AI agents do it: a read-only diagnosis of hardware, processes and bloatware, a risk-classified cleanup plan he approved, restore points before each of three change rounds, his full dev environment installed, and a selective migration in which an agent read the old disk and copied only what mattered, including his SSH key with restricted permissions, verified working. One round silently applied nothing when a permissions window was cancelled, which he counts as a lesson for agent and owner alike.
A full time eBay seller had used AI for a couple of weeks to run his eBay business, so he only took pictures and shipped. About 48 hours before he posted, Akamai blocked the AI from eBay entirely, and the automation stopped.
Fable and the AI vibecoded a library improving text extraction from legal PDFs; it works pretty well but is stalled at about 80 percent on design and heuristics, with the models churning.
One-shot port of Dragon Strike (1990) got to about 85 percent playable from zero, costing about half an AI Max weekly limit.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
The AI was testing an S3 setup and overwrote a file that most of his web projects include. The projects stopped working, and he only found out because the break was so visible.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.