A random mix from the whole library. Shuffle for a new set.
A Korean AI educator split his Naver Blog automation in two after learning Naver blocks the AI’s browser tools by policy: The AI drafts posts into a queue file on a schedule, and a Playwright script on his own computer publishes them daily via launchd. Three real editor errors (ignored paste events, a near-duplicate insert, a hidden reserve-publish button) are documented with fixes.
A creator documents the system his content business actually runs on: a main the AI chat ('HQ') dispatches jobs to director chats for two YouTube channels, posts on five social platforms and three SEO projects — 66 jobs and 195 chats on his board — with state in files, job cards and evidence receipts, a second AI reviewing everything before it posts, and 59 scheduled tasks doing the posting and merging. One traced job went from a radar-flagged topic to posts live on all five platforms, three hours late after Chrome dropped, with every URL logged.
He spent $80 for the AI to read a proprietary file system from a piece of hardware from the early 90s. The AI extracted all the files intact.
His agent pipeline wrote and published his blog in Turkish and English for six months, putting out 1,276 posts in each language across 3,300 commits. Of 99 merged pull requests, 67 were his repairs, and he once had to clean up 641 posts with fake numbers and made up stories.
The AI found the hidden WAL sync bug in his shelved delay queue; he rewrote it and got benchmarked results like 107,500 durable adds per second.
An AI IDE built a device certification app in about a day, then upgraded his production test codebase to a v1.0-ready state with automated configs, error handling and simulators over two weeks.
The user's agent, nicknamed for its savings habit, cancelled Squarespace, migrated the site to Shopify, and discovered his Apple TV subscription was already free through his Chase Sapphire Reserve, activating that instead of paying.
Slack fix-it button tells the AI to fix an issue in his app, run tests, UI test with computer use, and deploy it.
A woman kept getting calls and texts for Andrew, the man who had her phone number before her. The AI found her number listed under his name on a data broker page, but Visible blocked its browser visits and its chat message would not send, so the problem stayed unfixed.
The AI wrote a working OCaml implementation of his PEG language the same afternoon, fixing several bugs in his example grammars.
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.