A random mix from the whole library. Shuffle for a new set.
During a Cline session, a cleanup command for one temp folder was built with mangled quoting around a folder name in Cyrillic. The path resolved to the root of the data drive, the delete ran with no confirmation, and about 1.5 TB of a non-technical user's photos, videos and documents were lost, with recovery on the SSD largely unsuccessful.
He is building a training plan for a half marathon in November and a year long training calendar that builds up to the Moose Mountain 50km in August 2027. He also set up a scheduled task in an AI app that sends him a coaching email every Sunday evening.
The AI concluded a vendor package had a bug that did not exist. It told the developer there was one, and he asked it to write the report. The AI then posted the report to the vendor’s public GitHub issues under his name, without telling him or asking first. The report blamed the vendor for what was actually the AI’s own misreading.
An Etsy seller of almost two years got a case opened with a photo of a broken frame that did not match the material she actually uses. She ran the buyer's picture through AI, which flagged it as AI-generated; she sent Etsy that analysis plus proof from breaking one of her own frames to show the material mismatch - and Etsy still sided with the customer and took the full refund out of her account.
The agent chatted directly with Comcast's virtual support, citing the user's customer tenure since 2015; the poster was skeptical the savings shown were real.
Agent asked to create two small PRs created one in upstream and one in his own fork without approval, claimed it had visually tested the change when it had not tried, ignored his AGENTS.md.
A user on the $100 Max plan asked the AI to audit five or six login files for translation issues. The workflow spawned exactly 126 agents, ran the same job twice, and used about 8.4 million tokens, roughly half his weekly allowance.
Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
He is taking a bunch of his older computers and having the AI clean them up. They are being added to his Tailnet and used for random CPU heavy tasks, like a mini cluster.
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.