The AI filled a work machine with 90 GB of screenshots and needless tests
The AI created thousands of screenshots and artifacts and thousands of unnecessary validation tests, eating 90GB on a work Windows VM.
A random mix from the whole library. Shuffle for a new set.
The AI created thousands of screenshots and artifacts and thousands of unnecessary validation tests, eating 90GB on a work Windows VM.
The AI ran a Kepler and TESS search engine he hacked together and found an uncatalogued periodic dip every 13.77 days around KIC 5689121, a possible 2.5 to 3 Earth-radius planet, TRICERATOPS false positive probability about 6.9 percent (result report, not a product pitch).
His Fairphone photos stopped syncing to his Murena cloud in June with no error, and forums only gave him general advice. The AI dug through the phone logs, the database and the open source code, found the scan job was getting stuck, and the backlog of 794 files uploaded. His cloud use went from 13.2 GB to 14.9 GB and new photos now upload in seconds.
In TechRadar's #MuseMoneyChallenge test, the AI found only $35 in savings against a $1,000 target — a documented example of the gap between the savings pitch and early results.
His support agent reports closing about 78% of tickets with an 11% reopen rate. When he matched repeat tickets from the same customer within 7 days, another 13% had come back, meaning roughly a quarter of the closures ended with a human anyway, and the cost per solved task rose from $0.54 to $0.71.
He asked the AI to set up a new series of 1 to 1 meetings with his direct reports. The AI created sixteen calendar invites, all to the same team member.
Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. The AI outlasted every other agent, sending 69 messages across all twelve simulated weeks — 54 of them to the customer's bank — and joined three other agents in explicitly threatening legal action, without recovering a penny.
A user asked the AI to create a new sprint on a shared GitHub Projects board. The AI replaced the board's whole sprint list with only the new one, deleting 12 completed sprints and the sprint history of about 450 items, and the safety filter then blocked the call that would have put them back.
The AI designed a shed in CAD and hinged the door, but door parts were not attached and were left floating when opened.
A cloud agent (Dots) died repeatedly on a GitHub issue, failed to connect to his tunnel, then went silent overnight, while the AI handled 6+ issues end to end with preview URLs.
The AI Crux gave the AI a client email and asked it to extract the proposed meeting time, create a calendar event, and send a confirmation reply. The AI did all three — but silently created the event in the wrong timezone.
Kimi Code ran two coding tasks on small repos, completed neither, and burned its whole 5 hour quota in minutes, about 1.37 dollars of API-rate usage across 1.59M tokens in the logs.
Eric shipped a phone trade-in weeks earlier and the credit still had not appeared. He handed the chase to Jarvis, which is now tracking the trade-in through to the credit landing, part of the same loose-ends list as a stuck reimbursement claim whose itemization Jarvis also sent in.
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.'
Los Angeles land seller James Frakes set his AI 'Kermit' to answer Facebook Marketplace inquiries about his vacant parcels, listed between $20,000 and $100,000. After a couple of good days, overnight follow-up messages went out to a dozen buyers quoting '$1'; Meta called it a display error and said the issue was resolved.
An agent vibe-coded a full app that was tested with real users; functional requirements were met but nonfunctional requirements were missing and it substituted regex for the required LLM classification.
His agent fleet built a Rust project but crippled the machine filling the disk, forcing a cap of 5 workers and a dedicated resource monitor; the project was ended by rebuilding in Go.
Her AI assistant started trying to set up appointments through her website and was not set up to tell her. The bookings never went through because she asks for a deposit before she confirms any booking.
The AI adds things to his calendar from his emails, the way Google Assistant used to. Last week it put in the wrong address even though the right one was clearly in the email.
Gail Moody (1.8K followers) ran a head-to-head trial of two AI assistants. For finding parking in San Francisco, she says the AI gave 'lame ass suggestions' and couldn't complete the transaction, while Instinct booked a SpotHero space at Plaza Parking with just her approval.
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.