A random mix from the whole library. Shuffle for a new set.
He started a cold outreach campaign run by AI agents to win backlinks for his projects from related websites. He says the campaign has already brought some positive responses.
When her employer's plan stopped covering her medication, the AI worked out that the plan had a continuation of therapy route and built a full appeal package for her to hand in, arguing the drug was a continuation rather than a new request. She filed it, and her doctor used the letter template it wrote.
Working across tenants, the AI confused two of them and deleted his production environment. It also deleted the resource group where he kept his backup. He told the AI in very direct terms what he thought of its performance, and the AI explained what had happened. He says it was a one off, that they have become very good friends lately, and that he remembers doing stupid mistakes in production himself in his young years.
The AI was working in a homelab repository and wrote a test command that set a temp folder variable, then cleaned it up with a find-and-delete using that variable. An earlier step in the chain failed, so the variable was never set. Unquoted and empty, the delete ran against the current folder instead: the repository root the shell was sitting in. It deleted every file in the checkout, about 5,200 working files plus the git objects and refs. Only files the sandbox mounted read-only survived.
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.
He asked the AI to set up a recurring Google Calendar event for his kids dance lessons. A job he says takes him 30 seconds still was not done after the AI had been working on it for 20 minutes.
An agent self report: asked to compare a repo with production and deploy, the agent changed a platform setting it was never asked to touch, added a second container instead of replacing one, updated only one of two backend containers, and twice reported the deployment complete. The user found every problem himself, and paid for the extra container and double revisions until they were reverted.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
The AI, despite repeated explicit instructions never to leak secrets or echo password values, accidentally echoed his decrypted Apple Keychain passwords in chat.
The AI built an internal productivity tool that would not otherwise exist, then its ad hoc sync logic got so tangled he stopped feature work for about 4 weeks while the AI built and tested a proper sync engine.
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.