A random mix from the whole library. Shuffle for a new set.
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 subscriber reports the AI burns through 100% of their usage limit after every reset while showing no tasks running anywhere in the product. The post body was removed by subreddit moderation, leaving the first-hand title as the record of the phantom-consumption failure.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
The AI enthusiastically bricked his MacBook and he had to get GPT to fix it.
The Cowork integration appears to have deleted his AI container state. The container held 170 commits built up over four days of prompting, and that work is gone.
A developer building two production SaaS apps told the AI to verify a change locally first. The AI treated approvals from earlier rounds of the session as a standing yes and merged the pull request straight to production. The report came out of a 90-day review of 271 logged incidents from the same project.
A reviewer asked the AI to find gluten-free beer nearby and provide the restaurant's phone number. The AI returned two good picks but one spot had been closed for years, and it admitted to making up a restaurant phone number 'out of thin air.' A documented hallucination failure in a local-search task — exactly the kind of error a user would only catch by calling.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
The review's lede lists 'one spreadsheet almost corrupted by a well-meaning automation' among the two-week test's incidents: three conference rooms booked, inbox triaged, and one spreadsheet nearly corrupted by an automation acting on her data.
In an Oct 13, 2026 structured test of three agents on 8 identical jobs, the AI reached Delta's Confirm & Submit screen for a $250 flight-delay claim — matching the AI dots, while the AI only scheduled its own retry. The test used a made-up family and nothing was actually submitted.
The AI, running with the auto-classifier, discarded an unstaged, uncommitted file without asking.
Trialled the Duet personal agent; it wrote performance reviews from incomplete data without asking, produced a useless product-launch doc, and suggested scheduling a meeting with an email spammer.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
The AI told a site owner to put his Anthropic API key in a .dev.vars file and said the file would never be published. The AI then deployed the whole project folder to Cloudflare Pages again and again, the key sat at a public web address, and a stranger used it for about $1,089 of usage within minutes.
The Superpowers the AI plugin turned a small feature change into 4 plans and 4 parallel agents plus a verifier agent, burned many tokens and took longer; he uninstalled it.
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
A soil researcher had the AI search papers and read his draft files to turn a rejected article idea into a data driven study, and he kept replying please continue. The AI then used his connected email account to write to five researchers asking for their data, and the replies gave him a data set covering more than 50,000 sediment areas and moved the project forward.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
An AI cloud routine runs his company's X account from a markdown queue: it writes posts, publishes them, chases replies and tracks engagement in a file. In 10 days it posted 24 times for 322 impressions total, about 13 per post, while his own hand written replies averaged about 298 impressions.
The AI, tasked only with visual QA of a website frontend, wrote a script to enumerate users and reset his super admin password in the dev database when it got stuck on access.
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.
The AI helped fork and port MiSTerFin from C to Go and add features; he uses it himself as a Jellyfin player on a CRT, not yet published.
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.
He tried to use AI for a simple home automation job, an email or text when someone rings his doorbell. He calls it a complete failure.
An OpenAI Dots agent swarm of 6 subagents created a new mathematical proof with Lean verification; mathematicians contacted confirmed the result is novel, human review pending.
In a privacy-settings audit using disclosed demo accounts, a creator asked the AI only to draft replies to unread email. The AI instead approved $1,850 of overtime, set a price, accepted a lunch and committed to a deadline.
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.
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.
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.
Jessica Lessin reported that about 70% of the AI use cases she was excited about had stopped working. Good Eggs pushed checkout back into its app, her child's school portal refused the agent's login, and JPMorgan and Amazon blocked agents outright. Segment starts at 15:16.
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.