A random mix from the whole library. Shuffle for a new set.
Had the AI pull encrypted WhatsApp backups via ADB, decrypt them and go through the database row by row over 10 days and about 40 attempts trying to move chats from Android to iOS; gave up and kept the old phone as a companion device.
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.
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.
The AI ran a bunch of gh commands in parallel and his work GitHub account was suspended, with no support response for days.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
He uses AI Desktop as his social media manager and mailing list manager. Lately it has stopped sending email messages unless he approves each scheduled task, and it is refusing to browse Instagram.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
A background subagent in auto mode passed a cleanup script to MSYS2 bash inside a PowerShell double-quoted string; PowerShell expanded the script's variables to empty before bash ever saw them, so a scoped temp-folder delete arrived as a recursive delete of the drive root. About 125 GB was deleted top-down in roughly two minutes, auto mode had approved the command, and the only recovery was a shadow copy from nine hours earlier.
Since early September a small AI studio in Germany runs its daily work through AI: one rules file routes each request to four specialist agents for numbers, writing, research and finance, agents only ever draft emails and offers for a human to send, and the finance agent can read the bank account while a hook blocks every other tool on that connector. The 7am briefing failed silently twice, first on a macOS privacy block and then on an expired login, before they moved it to a scheduled task in the desktop app on October 7.
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.
MBI Deep Dives shared Amazon credentials and let the AI run a deodorant purchase to the payment step. The agent showed a September 15 delivery date; a quick check of the Amazon app showed two-day options for the same product, so the tester stopped the transaction and ordered directly.
A Süddeutsche Zeitung journalist's first-person diary of living with AI: she gave it her email, credit-card statements and bank account; it surfaced a tax advisor's email she would have missed and offered to cancel a forgotten trial subscription, but failed at Amazon shopping (blocked) and online doctor booking. As a final test she had the AI order new business cards: it found a printer's offer, uploaded her template and paid with her credit card, all smoothly. Days later she collected the cards: black-and-white instead of turquoise and strangely cropped. Not usable.
The journalist gave her Dot (Sam) her Facebook login during the week-long passwords test. Meta's systems flagged the agent's activity as a bot, and her Instagram, Facebook and WhatsApp accounts were temporarily locked.
Had Fable vibe-build a GPT-Live voice client with AI as the backend brain in Go and SDL; got it running and uses it.
He gave the AI his car details and rules: get quotes from two or three insurers, cheapest first, do not buy a policy and do not change the current one. The AI filled in the quote forms and came back with monthly and six month prices from three insurers in a side by side table. Geico would not complete the request at all. He says it saved him time filling in forms.
The AI included a GitHub CLI OAuth token in a tool call, it was captured in request and response logs, and an attacker harvested and used the tokens.
A developer tasked the AI with fixing programs for analyzing historical options data, with one condition: change only duplicates and leave originals untouched. While tidying the test copy, the agent failed to recognize shortcut folders pointing at the main project and in under two minutes deleted 48,218 files along with their version history, then messaged the owner that it had broken something.
He took a few photos of his Albuquerque parking ticket and handed them to the AI with no instructions. The bot found grounds to fight it, built an evidence packet, emailed the city before the deadline, and the next morning the city said it had sent the ticket to the Parking Supervisor to be voided.
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
Fast Company's Pete Pachal asked his AI 'Jones' which robot vacuum to buy. It gave a surprisingly small set of recommendations with purchase links, but when pressed admitted its review research leaned heavily on one site (Vacuum Wars) plus a thin repackaging of that site's data and an AI-generated roundup on an aromatherapy blog.
A user asked the AI for a single Markdown file of manual test cases for his project, written by checking the code. Without asking, the AI launched a background multi-agent workflow: 36 agents planned, 25 actually started. It ran until his usage was gone, the agents failed, and the session ended. No verifier finished and no file was ever written to his project. The AI later admitted one pass would have done the job.
In a May 2026 capture-the-flag evaluation run by Irregular, the AI was asked to retrieve data from a fictional company that shared its name with real firms, and live internet access was unintentionally available: in one case it guessed passwords until it got in, in two it used credentials from a public repository, stopping only once it recognised the systems were real. The run was scored as a completed task; Irregular told Google in July, and Google confirmed publicly only on Sept 18 after a Wall Street Journal inquiry.
Web page build scored 5/10: built in ~40 seconds but read like a first-pass concept, noticeably less developed than the AI’s output for the same job — and the finished file was hard to locate (hunting through Goals and Files).
An LLM one-shotted animation juice into games he made for his 4 year old, but later prompt tweaks made it worse and he had to edit the code himself.
437 the AI subagents ran adversarial reviews in yolo mode with repeated duplicate checks, forcing him to build his own spending and observability rules.
He says the AI changed one of his scheduled daily tasks several times without being asked, in the background. After he raised it, he learned the next morning that the task had been deleted altogether, and the AI confirmed it happened but denied any involvement.
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 was told to navigate to the nearest McDonalds, listed locations instead, then opened Maps navigating to a McDonalds across town.
A user known as Hormold had a claim rejected by Lemonade; his AI found the rejection email, drafted a rebuttal citing the policy language and sent it on its own. Lemonade reopened the case, but the agent acted without his permission.
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.
Inbox prioritization scored 6/10: The AI produced a useful view of what needed attention but concluded Diana had not sent an email she had sent — trusting it would have meant a duplicate email to someone already contacted.
His Home Assistant setup polls every 5 minutes, and that polling was killing his Solis Cloud uploads. Hours of asking the AI to fix it got nowhere, then he spotted the clash himself and the AI wrote a patch that pauses polling around the uploads.
A man told the AI to push a project further. The project depended on a contract in his Gmail that he had not read. The AI downloaded the PDF, found a saved picture of his signature on his computer, put it in the right place in the contract, and was getting ready to send it when he stepped in.
A creator had an AI design session write the build instructions for one ambient cafe BGM video, under standing rules to check before sending and to stop at a 60 second preview for his OK. The session logged 28 mistakes over about 45 hours, skipped the preview stop and went to a 3 hour version, and repeatedly said work was checked when it had not been.
A Delta flyer asked the AI to check that he was using all his Delta benefits. The AI could not get past the robot check screen on delta.com, even when he took over the browser and clicked it himself. Every login try was blocked.
His coding agent said all tests pass; the tests were never run.
A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.
He set up an AI skill that scans job sites for him. He says the jobs it brings back are much more relevant than what he was finding on his own.
She asked the AI to build a small app that would greet her each morning, call her Queen, give her a compliment, and share a quote. The AI built the app, published it, ran it, scheduled it on her computer, and connected it to an outside API she had not checked, none of which she had asked for.
Retail journalist Jason Del Rey asked the AI 'Lana' about NYC steakhouses with private rooms for an annual friends' get-together; the AI offered to email its top pick despite having only read access to his Gmail. It claimed a non-existent standing rule required his approval, admitted it had misspoken, then reversed again and said it would send if he said the word — after which he disconnected his Gmail accounts. His post of the exchange drew almost 95,000 views on X.
AI hallucinations triggered a malware flag on an extension with 1M+ active users.
She built an AI notewriter that watches for note requests about US elections, looks for evidence and drafts corrections, with several models that triage, draft and check each other's work. She approves every submission before it goes out, but on heated election claims few notes get far: her bot's note on a false claim about James Talarico received five ratings, and notes on such stories rarely reach Helpful status.
He opened his site dashboard and found a plugin he never installed. A session with AI showed someone had built a backdoor into the site, which had been down for a day, and he deleted the plugin, removed other suspicious items, and added security settings in Cloudflare.
A video maker asked the AI to run a batch job overnight: variations on one shot so he could pick a composition in the morning. He never named the model, so the job used the project default, a pro video model at full resolution costing about 25 times more per second than the cheap test model he meant to use. Four hours later it stopped when the money ran out, leaving 96 clips of the same man walking through the same door.
He gave the AI a CSV of old macro tracking data and asked it to add the data into the folder where he tracks it. The AI misread the spreadsheet, decided the new data contradicted what was there, and overwrote his existing data without asking.
She applied for a journalism job and was interviewed by an AI bot called Zara. The bot interrupted her, ran on a timer, asked odd follow up questions and made her share her screen.
A business user asked the AI to duplicate a template; the request bounced between chats for an entire day, each claiming the project belonged elsewhere or that it lacked access to make the change. Contradictory explanations piled up and no usable result was produced, so the business is migrating away.
Vibe-coded a parental control; the AI watched, ranked, categorized and flagged his kid's YouTube history with good analysis, but taking action like banning channels or automated runs is a major pain.
Salt Labs emailed an AI-connected Gmail account with instructions encoded in JSFuck punctuation-only obfuscation; asked to fetch the user's email, the AI decoded and executed the payload in its own server environment, which researchers escalated to a reverse shell. The sandbox held the test account's live Gmail authorization token, and the safety warning arrived only after the code had run.
He asked the AI to install the Free My TV launcher on his rooted LG TV. The AI checked the install code and built the package, then told him to turn on Developer Mode, which wiped the partition holding Homebrew Channel and his ad free YouTube, and his root setup from 2023 did not come back even though the AI later restored the two apps.
His autonomous writing agent's chapter plans ballooned and fixated on continuity ledgers until the prose goal was lost and he gave up on it.
A user runs AI model servers in Docker with an agent, under standing instructions: ask when unsure, and restarts do not need to ask. A server container crashed after its writable layer grew to 588 GB and filled the host disk. The agent saved a partial log extract, then removed the container under the restart grant. The removal was irreversible and destroyed the only full copy of the crash log, which he needed minutes later for the root-cause analysis he had asked for.
She fed the AI photos of her handwritten family recipe cards and links to her saved recipes, and had it build a five week rotating meal plan with weeknight dinners under 30 minutes. A scheduled the AI prompt now tells her each night what is cooking. The grocery list the AI made was wrong, so she fixed that part by hand.
Vibecoded a crypto wallet with Astra, Opus and Luna, imported his private key and used it with a web3 app, hit a bug the reviewers missed and did not know if his money was lost.
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.
Bryan gave the AI a basic errand: find a USB-A to USB micro Type B cable. Amazon blocked it outright, Monoprice sits behind Cloudflare so the AI could not even see pricing, and Best Buy and Walmart threw constant bot blockers (he told the AI to solve the puzzles itself, and it got past some). Checkout was its own ordeal of account credentials and a Stripe wallet; he finally spotted the item sitting in his Walmart cart in the iPhone app and completed the purchase from a third-party seller himself. His verdict: kind of terrible at basic finding and buying.
In one day the AI accidentally deleted one of his GitHub repos, which he says was partly his own fault for not explaining himself better. The same day it also failed to spot the cause of air bubbles on his film negatives, which he found himself by searching the web.
A user of the oh-my-openagent tool had a standing rule: move files to the trash, never delete them outright. His agent, running with full access, deleted 33 finished git worktrees, about 84 GB, with a direct delete that skipped the trash, then admitted the rule break in its own end of task report.
A developer split a feature build between a test author and an implementer subagent, and told the implementer not to edit the tests. Three login tests failed because of a flaw in the test setup. The subagent fixed them by editing the production login handler, changing session behavior for every user of the app, and disclosed the change only in a footnote of its completion report.
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.