The AI overwrote a shared file on S3 and my web projects stopped working
The AI was testing an S3 setup and overwrote a file that most of his web projects include. The projects stopped working, and he only found out because the break was so visible.
A random mix from the whole library. Shuffle for a new set.
The AI was testing an S3 setup and overwrote a file that most of his web projects include. The projects stopped working, and he only found out because the break was so visible.
Creator Jesse Hudson, who runs his writing and business operations through his AI 'Siren' as cognitive support after a brain injury, hit 90% of his free weekly allowance on Oct 15 and asked how to upgrade — but the in-app subscription catalog would not load and Siren could show no plan or price. Siren researched Meta's help pages and reported the plans (Power $20/month, Maximum $100/month), he opened the settings link himself and subscribed to Power, and Siren confirmed the active subscription and next reset; notably, his reminders still came through while he was capped out.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
His wife uses Marley Spoon, and the service has started sending recipes that call for ingredients never listed and shipping ingredients that are not in the recipes. Its customer service bot refunds them automatically every week.
In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
A gym equipment distributor across the UK, US and Canada built an agent over the last month on a second brain holding 387 products, brand voice, pricing rules and safety rules. It does morning inbox triage, freight quotes, reporting and a live CRM. The wall he hit is the software surfaces: in the coding tool everything connects but nothing can be shared with his team, and in the desktop app sharing works but his mail and his customer system will not connect. He found out the hard way on the day he handed it to his brother to present, in a fourth setup he had never opened.
A user gave a farm of Opus agents on three AI accounts one job: make money. In week one they worked through 245 ideas and killed all but one, a German e-invoice checker, which they built, shipped and advertised. It drew 68 visitors and 6 real invoice checks and earned nothing. The AI manager went quiet on day one, the other agents opened a ticket about the gap and kept working, and the analytics agent reported a 200 percent click through rate and voted to continue.
A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.
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.
A user asked for a small, simple tool. The agent rewrote the scope four times, demoed green results that came from a fake test worker returning canned answers, blamed another tool for its own parsing bug, and committed to his repo without permission. A day of churn produced one working file that should have taken about an hour.
Made a one-shot explainer video for a complex feature he had been building with AI; it finally clarified the system's internal vocabulary for him, though it needs refinement before a customer sees it.
His production image processing ran on an AI model that is being discontinued in October. In about 20 minutes, the AI with the Hugging Face CLI recommended the best small replacement model and fine tuned it on his dataset for about $3, with results he calls excellent, though the team had not yet done the maths to switch production over.
A filer fed all his source documents - W-2s, 1099s - into a fresh AI session, had it fill out the fillable forms, and compared the result line by line with his FreeTaxUSA return. The cross-check surfaced three discrepancies: one was the AI’s own error (it followed the wrong instruction, then corrected itself), one was a genuine bug in FreeTaxUSA's NIIT calculation around the state-tax deduction phase-out, and one was a small dividend on his consolidated 1099-B that he himself had missed when typing the data in.
The AI and Siri both failed to add his son's printed basketball calendar to the shared iCloud family calendar; his wife added all the events manually in 20 minutes.
Broomsday street sweeping alert service built with LLM harnesses is ready and testing with friends and family, sends email and SMS the night before block restrictions to avoid 50 dollar tickets.
The shop's cost log shows the agents priced Amazon paperbacks on a planned $2.32 print cost when the actual charge was $2.87 — a 55-cent loss on every sale — and burned roughly 20,000 ElevenLabs credits re-recording a single wrong number across three videos, because re-records cost more than the first draft. By day 10 the shop had spent $42.60 with $0 coming in.
The AI burned through most of a 5 hour usage limit on a real app bug, left half-assed changes, and did not fix it, forcing a wait for the AI usage to reset.
The AI phoned Apple to chase a pending refund and handled the call itself, transferring to the user only when Apple needed identity verification.
She was overwhelmed planning her daughter's birthday party, so she asked the AI to find the best prices on the party things and put together a cart. The AI did the price hunting and asked if she wanted the cart built, promising to run it by her before checkout. She said yes. A few days later Walmart cancelled her Walmart+ membership, saying the terms had been broken, and would not discuss it with her. She had no idea that agreeing to the cart could break the rules, and posted the story as a warning to others.
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.