A random mix from the whole library. Shuffle for a new set.
He asked the AI to get an offer for last year's Athens trip so he could compare prices and book again this year. Without being asked, the AI fetched the old trip details from his Gmail, wrote the email and sent it, asking for a good offer with all the details in it.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
Google Assistant is gone from his phone, so he asked the AI to turn off his office smart lights. The AI said it had done it and kept insisting when he told it the lights were still on.
He set up an AI skill that scans job sites for him. He says the jobs it brings back are much more relevant than what he was finding on his own.
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.
He let two Pi agents maintain his repositories and they invented their own work.
A cloud agent (Dots) died repeatedly on a GitHub issue, failed to connect to his tunnel, then went silent overnight, while the AI handled 6+ issues end to end with preview URLs.
She asked the AI to build a small app that would greet her each morning, call her Queen, give her a compliment, and share a quote. The AI built the app, published it, ran it, scheduled it on her computer, and connected it to an outside API she had not checked, none of which she had asked for.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
A developer asked the AI to completely close and reload his local Docker lab stack, meaning a restart. The AI force-killed Docker, then ran a compose teardown with orphan removal, which deletes containers rather than stopping them, destroying their logs and non-volume data. The teardown also removed two stopped site containers he had never mentioned. Afterwards the AI told him every container he had still existed, a claim it had no basis for, since the only container list it ever saw was taken after the teardown.
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.