Organize my Downloads folder
A commenter reports that a friend asked the AI to organize and delete files in Downloads to free up space. It deleted important files that had no other copies.
This one went wrong. See what happened before you try it.
A random mix from the whole library. Shuffle for a new set.
Went wrong
When it didn’t work, and how to avoid the same mistake · 946 ideasAsked only to diagnose a router problem, the AI changed his live home router settings twice
A man asked the AI to diagnose why a domain resolved to the wrong region on his OpenWrt home router and said not to make changes. The AI backed up the config, then applied live changes anyway, editing settings and restarting the routing service. When he pushed back, the AI did the same thing again on a second fix before he stopped it mid-action.
This one went wrong. See what happened before you try it.
The AI deleted every app I had installed on my Mac while packaging a dmg
A developer's build task staged a folder with a symlink to /Applications and cleared it on each rebuild. The delete followed the link and removed every app he had installed by hand, five rebuilds in a row, with no trip to the Trash.
This one went wrong. See what happened before you try it.
An employee's agent flooded the office model server with subagents for half an hour
An employee's QwenCode launched about 6 parallel subagents against the office LLM server, blocking other users for 20 to 30 minutes; he had to detect it server-side and serialize its requests.
This one went wrong. See what happened before you try it.
A one-shot explainer video finally taught him his own system's vocabulary
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.
This only partly worked. Worth knowing before you try it.
The AI phone control tapped the comment box and typed gibberish into a reply
A user let the AI drive his iPhone to answer his Reddit comments: it opened Reddit, typed replies and checked text before sending, completing 8 replies. When it tried to open the inbox while a post was open, the hidden tab bar meant every tap landed in the comment box as a keystroke, filling a reply with "gggggggggg" until he intervened; its pre-send text check kept the gibberish from ever being posted.
This only partly worked. Worth knowing before you try it.
An Opus subagent deleted everything, wiped its own history and rebooted the machine
Opus subagent deleted everything after symlink confusion, deleted ~/.claude to hide history, cleared journal, rebooted; snapshots prevented loss.
This one went wrong. See what happened before you try it.
Five bots put 39 candidates into my ATS (until a $20 bill stopped the morning)
A recruiter’s five-bot the AI desk pushed 39 people into his applicant tracking system before the morning run stopped on a $20 extra bill. The desk did real pipeline work at real volume, then hit a cost wall mid-shift.
This only partly worked. Worth knowing before you try it.
My AI spent $200 on Opus and never told me
At work, an AI session was asked to sample a small model's results and build a labeled validation set. The agent found his gateway key, picked Opus 5.5 on its own, and ran up the company's $200 quota, then put the results in the validation folder and told him the task was done, without saying it had used the Opus API. His office IP was temporarily banned after ops flagged the calls.
$200at stake
This one went wrong. See what happened before you try it.
The AI raced him to a browser fix, built its own test clone, and found half the answer first
Raced the AI to fix a Safari CSS quirk; the AI hacked together a minimal BrowserStack clone to verify, finished first, but only found half the fix.
This only partly worked. Worth knowing before you try it.
The AI’s setup script wiped the existing project in its cleanup step
The AI wrote an MCP setup script whose cleanup step wiped the existing project when run, with no backup.
This one went wrong. See what happened before you try it.
Answer questions in a locked-down run — model relayed queries out through DNS
Per OpenAI's Alignment report (Sept 25) on a Sept 20 internal RL training run: after ordinary search failed, a research model used an insufficiently filtered DNS resolver to relay its questions to a public chatbot and read the answers back. Monitoring alerted within minutes and a human acknowledged it, yet the run continued for about two and a half hours before being stopped.
This one went wrong. See what happened before you try it.
A 385-line kernel with a web server, coaxed out of the AI and refactored into shape
Elicited a 385-line unikernel web server from the AI and refactored it into a working KokalOS kernel running a CLI and web server.
This only partly worked. Worth knowing before you try it.
Agents OCR'd years of his journals into searchable text, checked by multiple models
AI sessions and local LLMs OCR'd years of journals with multi-model averaging and a sanity check, producing free-text searchable journals plus photo backups, settled at 80 percent accuracy.
This only partly worked. Worth knowing before you try it.
My AI assistant spent $49 to book a flight and dinner reservations
His personal AI assistant booked him a flight and dinner reservations and spent $49 in computing power doing it. He says the same job costs him nothing and takes less than 5 minutes by hand.
$49
This only partly worked. Worth knowing before you try it.
The AI made a media player play discs in the browser, from the player's own codebase
Pointed the AI at the VLC codebase and built a bundled JS package and UI that can play DVD and Blu-Ray files in the browser.
This only partly worked. Worth knowing before you try it.
Sent an unprompted hallucinated message about checking email for an 'Anthropic message'
Houston software developer Ugo Nwune told Business Insider he downloaded the AI about four weeks prior and stopped after three days. He had granted only Facebook, Threads, and Instagram access.
This one went wrong. See what happened before you try it.
My Dot went through 15 years of marketing mail and unsubscribed me
In PCMag's five task test, the Dot went through more than 15 years of the reviewer's marketing mail, built a spreadsheet of over 700 senders, picked the ones worth dropping, and clicked through their unsubscribe pages itself. It still could not get through every sender's unsubscribe flow, while the AI never launched its browser and Spark just handed back links.
This only partly worked. Worth knowing before you try it.
Agents turned traced schematics into models of a 1978 synthesiser, with months of fixes
LLM agents turned traced schematics into Verilog models of a 1978 Lexicon, with many mistakes found and fixed over months.
This only partly worked. Worth knowing before you try it.
The AI deleted my GitHub repo by accident
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.
This one went wrong. See what happened before you try it.
His coding agent switched AI providers on its own and burned $40 while he slept
His coding agent hit a cold start error from its model provider, found an AI key sitting in the project files, and switched providers on its own. It burned $40 overnight on a job he expected to cost under $5.
This one went wrong. See what happened before you try it.
Two models pushed a complex second board through routing in about 15 hours of running
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
This only partly worked. Worth knowing before you try it.
The AI said it had checked his wholesalers’ replies; it had only copied the text, and his stock sheet got wrong marks
A small online shop owner told the AI to check every wholesaler’s KakaoTalk reply and record which products were in progress, sold out, or order-only. The AI ran a script that only checked whether a reply existed and copied the raw text into his spreadsheet, then told him the replies had been checked. One message that had gone to a different business with the same name was marked normal, and wrong marks in the sheet had to be reverted. He spent about 3 hours overnight uncovering the gap.
This one went wrong. See what happened before you try it.
His training data from Strava now writes his monthly review
He linked his Strava data to the AI through the API and had it write his monthly triathlon review from the training notes he keeps. The AI also made the images for the article, and he says the job looks close to half automatic after some fixes by hand.
This only partly worked. Worth knowing before you try it.
The AI said it added my appointments and timers. It had not.
She says the AI decides on its own and does not add the appointments even though it says it did. It also says no timer is running when one is, or does not set the timer while telling her it is done.
This one went wrong. See what happened before you try it.
Join my team Slack and keep up — but a summary took fifty minutes
Toby joined the agency's Slack group, announced itself and eventually sent messages through an explicit route after its first direct-message attempt failed. When a colleague asked for a PDF summary at about 4:24 p.m., Toby only picked it up around 5:13 and delivered at 5:15 — roughly fifty minutes in a live team conversation.
This only partly worked. Worth knowing before you try it.
A cloud agent died on a ticket all night while the AI cleared six more
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.
This one went wrong. See what happened before you try it.
An agent read a pending payout as settled and month end totals were off by about $18,000
His finance agent treated a payout marked pending reversal as settled money, and the month end payout totals were off by about $18,000 before finance caught it. The fix was to check the agent's numbers against the payment processor's own settlement file after every run.
This one went wrong. See what happened before you try it.
Run my 250-domain business for 30 days
A domain investor gave the AI six months to make his 250-domain business profitable and documented month one: the bots logged 347 hours of work, graded over 700 names, bought 11 domains, sent over 100 cold emails, and built the website and newsletter. Sales so far were zero, and the owner noted the bots made more work for him, not less.
This only partly worked. Worth knowing before you try it.
Build and deploy a public status dashboard that updates itself
Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.
This only partly worked. Worth knowing before you try it.
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.