A random mix from the whole library. Shuffle for a new set.
A background subagent writing a benchmark left a placeholder of minus one in a kill call. When the script ran, it signaled every process the user owned, wiping his terminal sessions, his other AI sessions, his desktop and his browser in one second.
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 Korean content operation handed three channels (Naver blog, Threads, WordPress) to an AI agent publishing at 9:00, 13:00 and 17:00 daily, logged over Oct 15-18, 2026. A rule requiring the AI review approval before publishing caused three consecutive zero-post rounds when the review step was blocked or could not find its command; after the human demoted review to advisory only, a full round finished in 33 minutes. The same topic posted at the same time drew 629 views on Threads versus 2 on Naver within four hours.
He connected the AI to DevonThink, the app where he keeps his documents. That gave him the help he needed for the huge job of sorting and tagging old documents he had saved before he used DevonThink, some of them from January 2020.
A solo developer spent about half a year building an AI pipeline of research, qualification, delivery and ledger agents meant to find, win and deliver paid work on its own. Across two cycles it discovered 10 opportunities, qualified none and won zero contracts, ending at a net loss — the system worked, but no client would hire an unknown automated service.
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.
The AI made a bad MCP call and wiped the contents of a Confluence draft he had open in his browser. He lost two hours of work.
A Spanish startup magazine recounts a Sept 28, 2026 post by Simon Willison quoting the AI directly: the agent's pickup auto-reply had assured a visitor, Usman, that the user was at home when he clearly was not; Usman showed up at the building around 9:15 and waited, messaging repeatedly, and nobody came down. In the quoted exchange the AI took the blame, apologized, and offered to change the pickup replies so they stop promising a presence it cannot verify.
He asked the AI to update his docs with his new API changes. The AI deleted his source files from his jj history instead.
The AI built an internal productivity tool that would not otherwise exist, then its ad hoc sync logic got so tangled he stopped feature work for about 4 weeks while the AI built and tested a proper sync engine.
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.