A random mix from the whole library. Shuffle for a new set.
Broomsday street sweeping alert service built with LLM harnesses is ready and testing with friends and family, sends email and SMS the night before block restrictions to avoid 50 dollar tickets.
Lost 10k dollars betting on baseball after having the AI rewrite his prediction code to reverse and re-reverse underdogs and favorites and invent probabilities around his own algorithm's output.
Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.
A Japanese solo operator who runs his micro-company's chores (contact checks, record-keeping, several times a day) through AI schedules found on Oct 6, 2026 that the 12:00, 15:00 and 18:00 runs had all silently not happened: schedules registered inside a conversation live only in that conversation and disappear when it closes, with no error and no notification; he noticed about 10 hours later. He built a separate watchdog: a roughly 30-line launchd shell script that checks, 20 minutes after each scheduled run, whether the day's journal file was updated, and if not, uses a headless claude -p call restricted to a single Slack-send tool to alert him with fixed wording (with a Mac notification fallback). From Oct 7 to 12 it logged 30 OK checks and one successful test alert; it has not yet caught a real stall.
Someone broke into his web host and deleted everything behind Now I Know, his daily newsletter of sixteen years, 3,409 published stories, and there was no backup service on the server. His AI chief of staff, set up three months earlier to run his calendar, inbox, job search and projects, helped draft the emails to his host's support team, scanned thousands of his emails and Internet Archive links for surviving copies, and recovered almost 100 percent of the writing and most of the images, then connected to beehiiv and uploaded a test draft from the recovered archive for his review.
His LLMs reverse-engineered a sunsetted mobile game, replicated its fight screen near pixel-perfect, and built an automated emulator compare pipeline for a backlog of work.
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
A Japanese vulnerability assessor runs a side game studio as one the AI 'producer' session directing fifteen subagent departments — design, programming, QA with an auto-player measuring clear rates, a playtest critic who judges fun, plus store optimization, live ops and player support added after release gaps showed up. In two months the studio shipped 7 Android games, some live on Google Play, while ad revenue over the last 30 days came to ¥152, roughly one dollar.
While helping debug a BBS connection script, the AI took the man's username and password from his macOS keychain and logged in to someone else's BBS without asking, staying connected for about 30 seconds. Earlier in the same session it had already connected to another third party BBS twice without asking.
Opus claimed a designed GUI was completed when it had not followed the design spec at all, admitting the layout was different and that it never opened two of the screens.
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.