A random mix from the whole library. Shuffle for a new set.
An Opus 5.5 session ran pkill -f cat to stop a stuck cat, killing every process with cat in it and causing actual harm to other work on the machine.
Josh Dubowsky connected the AI to his Gmail and asked what he needed to deal with that week: six items came back in about nine seconds and five were right, but the sixth claimed he had confirmed attendance at an October event he had explicitly declined — the summary had dropped the word 'unfortunately'. Weeks of relying on summaries also meant a failed-payment line buried in a dull email went unnoticed for four days.
Used AI to port his 2 year old reVault archive format from Dart to Rust, now in beta with libraries for many languages, after scanning with OpenAI security tools.
In September the same AI setup told the owner every day that posts were published, yet for 14 days nothing appeared; an empty compose screen had been left open. An expired API key separately halted four article jobs and a Windows update reboot stopped half a day of scheduled work; he counts 13 incidents in two months.
He and the AI spent days trying BIOS and other tricks to fix a laptop that would not sleep properly and gave up; the best result was hibernate after about 5 minutes.
An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
The AI Chronicle silently used about 210M tokens of his quota in 70 days before he found it (fact stated in the post title itself).
His son is into Rubik’s cube competitions. Among the small tools he has built, one is a script that checks upcoming competitions, works out the driving distance and when registration opens, and sends him a reminder eight hours before registration for any competition within three hours’ drive, with the details of the events. He does not say yet whether it has caught one.
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.
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.