A random mix from the whole library. Shuffle for a new set.
He used the AI for two weeks of daily Excel updates. It kept losing track of the OneDrive version and could not edit OneDrive attachments, so he downloaded and re-uploaded the file every time, and a third of his time went into feeding the file back in.
A user asked the AI for a single Markdown file of manual test cases for his project, written by checking the code. Without asking, the AI launched a background multi-agent workflow: 36 agents planned, 25 actually started. It ran until his usage was gone, the agents failed, and the session ended. No verifier finished and no file was ever written to his project. The AI later admitted one pass would have done the job.
Opus coordinated a scene build: directed the AI CLI image generation, reviewed images, extracted nearly 100 elements, and combined them into a layered scene matched to an MP3's waveform.
Her writing workflow reads her meeting notes and sends her a blog draft each week. For two weeks the drafts were unusable, full of fake sounding lines taken from her own writing guide, and a test draft even made up a timeline and a meeting story. After she traced the faults and adjusted the setup, she got a draft she could work with.
Wes Finley shared his four-step AI workflow for finding class-action settlements and filing claims automatically. Commenters chimed in with their own results, including $400 payouts.
He used AI and the AI to build a setup that automatically made one LINE sticker a day. He stopped the setup once he was happy just having built it, and the stickers stay on sale in the LINE Store.
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.
Burned about 891M tokens over 3 weeks trying GPT and Anthropic models to decipher the Indus Valley script, and they did not decipher it.
Last spring he gave an agent an API key with no cap on it. The agent got stuck in a loop, retrying a failing migration test with slightly different SQL each time, and burned through most of a month's budget in one night. Nothing malicious, just a loop with no exit. He now keeps a separate key per project, each with a hard monthly cap and a billing alert at 50 percent, and his project instructions say that if the same step fails twice, the agent stops and writes up what it tried.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
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.