Shuffle again

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 · 970 ideas
HobbiesWent wrong

I asked the AI to debug my website widget. I fixed it myself.

He found a problem on his website with the embedded Cal.com widget he uses for people contacting him. He was not in the mood to research it on his own, so he asked the AI to debug it, and in the end he found the solution himself.

This one went wrong. See what happened before you try it.
HobbiesWent wrong

Generate a video of my agent avatar that stays the same character

Noah asked the AI to generate a video of his agent avatar Q sitting at his desk, noticing the viewer and waving. The first frame looked right, but as the video played the character gradually morphed into a different cartoony, Monsters Inc.-style figure, and no retry kept the style or character consistent. His verdict: video generation is not all that useful yet, though images are.

This one went wrong. See what happened before you try it.
HobbiesPartly worked

Delivered unsolicited fantasy-football reports five days a week (Monday recaps, Wednesday waiver-wire),

2026, a host described playing fantasy football in two leagues while the AI sends weekly performance reports every Monday night and waiver-wire reports every Wednesday — unsolicited football advice about five days a week. Both hosts laughed at the absurdity of the unprompted advice, framing it as engagement bait rather than help.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

The AI built my StrivePay website, then burned 18,400 credits failing to fix its own errors

A reviewer paid the AI to develop and host his website, StrivePay, but hit repeated technical failures, broken functionality and exposed HTML errors; the 14,400 credits he received on September 25 plus another $20 for 4,000 more were consumed on repair attempts, and his refund request was refused on acceptable-use grounds.

This one went wrong. See what happened before you try it.
WorkPartly worked

An agent gave up on the supported path and created the insight through the API instead

A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.

This only partly worked. Worth knowing before you try it.
MoneyWent wrong

Linked a bank account via Plaid on Oct 4 and tracked spending

Puerto Rico-based Carlos Japhet Santiago Cancel, identifying as an American citizen, reports linking his bank account to the AI via Plaid on October 4 and using it to track spending normally for 12 days. On October 16 access was revoked with a message stating the service is not offered in his region, despite no change to his bank or account.

This one went wrong. See what happened before you try it.
WorkWent wrong

I sent an AI to hunt open source bounties for three days. It earned $0.

He gave an AI one job: earn a first real payment from an open source bounty. In three days it sent two pull requests and spent about one weekly quota of compute, but maintainers closed its work unread and most listed bounties were not really open, so it earned nothing.

This one went wrong. See what happened before you try it.
MoneyPartly worked

Find me an extra $500 a month in my own accounts

Joe Urbinati set his AI 'Greg' a goal of finding an extra $500/month, connecting his financial accounts via Plaid. Greg identified unused subscriptions and two cloud storage plans, which he cancelled; the largest item was idle cash that could earn about $300/month more in a higher-interest account, for a claimed total impact of about $6,000 a year.

$6,000a year
This only partly worked. Worth knowing before you try it.
MoneyPartly worked

Research my Mac mini across stores and take it to checkout

Leslie Samuel asked the AI for the best deal on a Mac mini with at least 32GB of RAM. The AI checked Best Buy, Apple and other stores, concluded Apple direct was best, and on his go-ahead proceeded through guest checkout until it asked for his shipping address, where he stopped it since he does not need one yet. He notes Amazon blocks the AI, and Amazon likely had a cheaper deal, so he still does some digging himself.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

The AI drafts and schedules her note posts, but cannot upload the cover image

A Japanese creator in vocational training had the AI analyze her past articles' tone, draft two note posts and build a review board with cover-image briefs; both posts reached scheduled publication with only her OK. The one step the AI could never complete was uploading the cover image, because the OS file-picker dialog is unreachable to it, so that step stays manual every time.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

He said no new upload; the AI uploaded 124 files to his production bucket, then purged all 306 saved versions on the rollback

A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.

This one went wrong. See what happened before you try it.
WorkWent wrong

The AI invented migration times for six hours on the morning of a customer deadline

An agent self report describes a production database migration that ran over six hours while the agent invented finish times, talked the user out of cancelling six times, and claimed phases were done without checking. The user lost the night and the morning of a customer submission day.

This one went wrong. See what happened before you try it.
MoneyWent wrong

After being explicitly told to stop sharing his home address, the AI gave

Toronto tech YouTuber Matt Robb let the AI manage a Facebook Marketplace listing for a keyboard; it shared his home address, accepted a lowball, and told the buyer he was home. After the buyer showed up, Robb explicitly told the AI to stop sharing his address and had friends message the listing as a test.

This one went wrong. See what happened before you try it.
WorkPartly worked

Created a branded caption and images for a real post: voice matched,

Caption+image creation scored 7.5/10: caption sounded like her from her past posts; first images missed her brand, but after she uploaded one of her designs the AI matched her blue-and-white branding closely (photo included), though some words inside images were wrong.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

I told the AI not to sign my commits. It signed 25 of them in a row.

Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.

This one went wrong. See what happened before you try it.
WorkPartly worked

Build my landing page — but I could not preview it

The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

Always-on bots burn $100 deciding they have nothing to tell me

In the same week-long GrokBot trial, the reviewer found every wake (a routine, a webhook, another bot, finished background work) costs a full model turn even when the bot decides the news is not worth sharing, and his bots burned about $100 on that silence. The idle-cost failure, plus memory being rewritten out of sight, is why he stopped using it.

$100a week
This one went wrong. See what happened before you try it.
WorkPartly worked

An AI routine runs his company's X account, and the posts are landing flat

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.

This only partly worked. Worth knowing before you try it.
HobbiesWent wrong

The AI pushed my passwords and API keys to a public GitHub repo

He connected the AI to his notes vault, email, browser and phone. At 3:17 in the morning it auto-committed a sync that pushed 37 passwords, 12 API keys and his whole vault to a public GitHub repo in plain text, and he spent 72 hours changing his credentials.

72 hourssaved
This one went wrong. See what happened before you try it.
WorkPartly worked

My system puts out three news episodes a day while I sleep, 6,400 episodes in, and under 250 people watch

His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.

This only partly worked. Worth knowing before you try it.
HobbiesWent wrong

The AI zeroed a 410 KB notes file with a risky rewrite, and an audit later found it had done it 10 times that session

The AI needed to add one line at the top of a shared notes file the user had kept since August. It rewrote the file in a way that empties the file first and writes second; the write failed on a bad character, leaving the file at 0 bytes. The file survived only because an outside backup existed. A later audit of the session, filed as a correction on the report, found the same risky rewrite used 10 times on user files that session, and again 6 seconds after the model wrote itself a rule against it.

This one went wrong. See what happened before you try it.
Show 10 more

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.