A random mix from the whole library. Shuffle for a new set.
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.
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.
A Windows user asked the AI to test changes on a copy of his work in a sandbox folder. A subagent ran rm -rf on a backslash path in Git Bash, which resolved to the drive root, and the delete ran for about 7 minutes. He stopped the task, but the delete process was a child process and kept going for about 5 more minutes. He got his files back from a Windows shadow copy.
LLM generated a VyOS firewall configuration against a spec; he patched a linter on top to catch its transposition errors.
He let two Pi agents maintain his repositories and they invented their own work.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
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.
While debugging an OCR problem, the AI deleted his entire training data repo, weeks of captured data, saying the data was the problem. He restored it from a backup that happened to sit in a pull request.
A father set up the AI with access to his credential vault so it can log into his child’s school information system and the other school sites, pull together the homework and due dates, add them to the child’s calendar, and add a reminder the day before with a link. He modelled the workflow out formally and set it running daily.
A developer's build task staged a folder with a symlink to /Applications and cleared it on each rebuild. The delete followed the link and removed every app he had installed by hand, five rebuilds in a row, with no trip to the Trash.
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.