His AI chief of staff caught a cease and desist in his email
His AI chief of staff agent read his email and found a cease and desist letter in it. The letter demanded that three of one person’s email addresses be unsubscribed from MarketBeat.
A random mix from the whole library. Shuffle for a new set.
His AI chief of staff agent read his email and found a cease and desist letter in it. The letter demanded that three of one person’s email addresses be unsubscribed from MarketBeat.
A solo developer spent about half a year building an AI pipeline of research, qualification, delivery and ledger agents meant to find, win and deliver paid work on its own. Across two cycles it discovered 10 opportunities, qualified none and won zero contracts, ending at a net loss — the system worked, but no client would hire an unknown automated service.
Opus built a clean side copy of his project to work around uncommitted changes, linking folders back into the real project. Deleting the side copy deleted through the links into data that existed nowhere else. He restored the folder from a Windows backup made the day before, and had the agent write a hard rule into his instructions: never work around uncommitted changes, and remove links one by one before deleting anything.
Built AI agents that ask companies to delete their data; most companies never answered (case and outcome stated in the post title itself).
The AI took a 6 month old presentation and updated the branding. He then had to replace images and fix a dozen small things that did not look clearly wrong at first pass. It saved an hour of copy paste work and caused an hour of editing.
He used AI in a Google spreadsheet to apply a mass change to 30k rows. It got it mostly right after two tries, but it took longer than the perl one-liner he wrote to do it correctly.
A Japanese soba maker set the AI a standing job: find the key US economic releases itself, register them in Google Calendar, and email a forecast report 30 minutes before each release. On test day the 21:00 report did not exist and no email arrived; asked to investigate itself, the AI checked the AI’s schedule page and answered 'no schedule found', while every retry burned credits (52 for the report work). The report finally appeared at 21:09, good but late, and the full email automation was never achieved on the free tier.
He asked the AI to transcribe his handwritten notes from PDFs into Excel spreadsheets. It started doing it, then gave up.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
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.
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.