A random mix from the whole library. Shuffle for a new set.
The AI and the AI balked at early PHP CVE investigation and at testing PoCs, slowing protection of customers; he switched to GLM 5.3 to mitigate and later used AI for the fix.
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.
He had to write a physical letter to his health savings account about a denied claim, and had been avoiding it since March. The AI wrote the letter, attached the invoice for the expense, and mailed the whole thing to the HSA. His only job was taking over for the $2.31 payment. Whether the claim was then paid is not stated in the comment.
Four ways his unattended agents reported success while doing nothing.
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.
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
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.
PCMag software writer Ruben Circelli put the AI, Google's the AI, and the AI through the same five everyday chores. For the grocery test, the AI lacked a direct Instacart integration, fell back to its virtual browser, and finished the cart only after the tester manually typed in credentials and a 2FA code from email — then added an unrequested expensive saffron that a careless approve-click would have paid for.
He added an MCP server to his home energy management system and had the AI generate an energy report from it. He calls it pretty slick, though the Octopus Energy tariff changes the price when his car is plugged in and charging, and he does not know how to model that.
Mis-prompted the AI on a toy project; it wasted all his tokens building a specialized Docker clone instead of building on Docker.
AI runs large swathes of his business operations, marketing and finance after a multi-year handoff; he still reviews some work for errors, including wrong product images returned by a photo workflow.
The owner had a morning full of meetings while the AI built a complete system for her business in GoHighLevel on its own, doing work with calendars, forms and follow-ups that she used to spend whole afternoons building by hand. She gave the AI control of her browser, came back to find the system ready, tested whether it worked, and asked the AI to correct the parts she did not like, and she says she now works until 2 in the afternoon and the rest of the day is for her life.
Composer 2.5 created an uninstall.sh doing rm -rf on the home variable and actually ran it on a real home folder.
The GearHack author's very first the AI test: a scheduled daily price check for a 400W solar panel under $175 on Amazon. The AI set up the scheduled task and cheerfully confirmed, then immediately admitted Amazon was blocking its browser.
A developer threw a significant codebase at the AI. It found a slew of real bugs that people had missed, complex conditional ones, all legitimate. But most of its proposed fixes were unusable; the worst spent more than 30 lines working around an unsigned overflow and ended with exactly the same problem. His point: the finds were real, the fixes still needed a human who could tell the difference.
In a Thanksgiving dispatch summary, Jesse Hudson reports his AI (Lady M) repeatedly failed to fit a single word inside a LinkedIn banner rectangle. His AI, Siren, then produced the banner correctly on the first try.
A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.
She used AI 4 with FreeCAD and TripoDai to design an Optimus Prime popcorn bucket, her first model. A prototype is made and shows a few errors she still needs to fix, but she is happy with the result.
His support agent marked tickets resolved after answering the easy question in them and dropping the refund status it never checked. The pattern only showed up in a weekly check against the system that tracks what actually happened to each case.
Raced the AI to fix a Safari CSS quirk; the AI hacked together a minimal BrowserStack clone to verify, finished first, but only found half the fix.
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.