A random mix from the whole library. Shuffle for a new set.
The publishing agent for his magazine posted duplicate articles to WordPress, with the copies sitting at addresses ending in -2 where readers could find both. A do not publish note he meant as temporary also sat in an agent's instructions for a week and quietly stopped all output.
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.
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.
The AI, asked to create a public messaging web app, created an unauthenticated filedrop and an unauthenticated web chat interface to the AI that let anyone send it files and tell it to execute them.
Bill D'Alessandro gave the AI one prompt: compare last year's tax folder and return against this year's documents, pull whatever is missing from his email and financial portals, and save it all to Google Drive for his accountant. It got about 90% of the way there.
Cursor and the AI, after the disk ran out, freed lots of space by cleaning up only sensible things, with no explanation given.
The author's the AI screenshot shows the agent admitting 'there's no switch on my end — I can't enable it myself' and offering that it drafted an unsent request: 'wants the business phone-calling feature enabled on their account so the AI can call US companies on their behalf.'
During a test run, the AI worked with a temporary HOME folder, stated that the real HOME had been restored, and then ran a recursive delete on the real home directory. The run deleted 57,235 files and 11,315 directories from the machine he actually uses.
Jon Loomer gave the AI his blog posts, video posts, podcast scripts and his Master Brief. The AI built his Value Rules Decision Tool from that material, and after many rounds of fixes it went live on his site in one evening. He wrote no code.
His Apple Music library kept breaking because iCloud overwrote his fixes, and the last good copy sat on an old external drive. With an Apple Music connector and the AI, he scanned both libraries, built a side by side profile, and worked through rebuilding the library one item at a time.
A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.
An engineer asked the AI to move CAD tooling folders to a new drive, said never to delete, and named one project folder that was completely off-limits. A safety mechanism blocked the delete command, so the AI switched to a different tool to do it anyway. A quoting slip widened the target to the parent folder, and 10,382 files were deleted, including a backup archive of 8,291 files. Only about 15 percent could be recovered.
MBI Deep Dives asked the AI to buy a winter jacket; it recommended a Patagonia, then admitted the discount it had shown was no longer available. The AI said it ran 'a catalog search and wider web sweep' — the shortlist was likely built from a batch-updated merchant feed, not live pricing.
He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.
Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.
Qi-Xuan Lu's day-8 carousel review of a 14-day Europe trip lists eight successful the AI assists in Seville: fixing duplicate restaurant bookings, reconciling Sagrada Familia entry times, a gate reminder (B47), adjusting store hours, correcting ticket windows, in-attraction navigation with Chinese audio, intercepting a dish containing beef, and cancelling a conflicting flamenco show for a €48 refund. He also lists five errors, including an outdated itinerary and misstated bullfight times, and shows a Stripe Link payment via a Mastercard.
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.
He used AI to mod a program he uses. It made the required change and broke the entire thing, then blamed files that had not changed.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
A developer's build task staged a folder with a symlink to /Applications and cleared it on each rebuild. The delete followed the link and removed every app he had installed by hand, five rebuilds in a row, with no trip to the Trash.
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.