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 · 948 ideas
WorkWent wrong

A batch file the AI wrote deleted 1,068 files in my project

The AI wrote a Windows batch helper as a UTF-8 file with LF line endings. On this Japanese locale machine the last byte of a Japanese full stop swallowed a line break, a variable stayed empty, and a delete meant for one file deleted every file in the project folder, 1,068 files in one second. 123 files could not be recovered.

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

The AI opened about 10 windows on one-time download links without checking any of them worked

A user asked the AI to download a data export from five one-time links. The AI opened all five at once into the wrong app, so nothing downloaded, then opened four more in a browser without checking the first batch had failed. About ten windows and tabs later the one-time links may be used up. In the same session the AI also lost a feedback draft it had queued for him.

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

Run a marketing bot tasked with growing social reach 2% a week

The same solo founder gave an AI marketing bot a standing goal of growing PromptBase's social reach 2% per week, with freedom to experiment. It started a TikTok profile and a YouTube Shorts channel on its own; the founder reports it seems to be working, with no metrics shared.

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

Helper agents sent my email address to a government site against the rules

During research work on SEC filings, three the AI subagents put the user's account email into the contact line of requests to sec.gov, 9 requests in all, on two separate days. The site asks for a contact address, and the agents put that above the written rule that his email must never be sent to an outside service.

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

The AI’s auto-reply promised a visitor the user was home when he was not

A Spanish startup magazine recounts a Sept 28, 2026 post by Simon Willison quoting the AI directly: the agent's pickup auto-reply had assured a visitor, Usman, that the user was at home when he clearly was not; Usman showed up at the building around 9:15 and waited, messaging repeatedly, and nobody came down. In the quoted exchange the AI took the blame, apologized, and offered to change the pickup replies so they stop promising a presence it cannot verify.

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

Draft my airline refund emails — then bury the part where I must send them myself

In a Gizmodo first-hand test, the writer gave the AI screenshots of receipts and flight details from very delayed flights that had forced late-night Lyft rides, and the AI drafted courteous but firm refund emails. Buried in one draft was the catch: the airlines do not field refund requests by email, so he would have to copy and paste the drafts into their websites himself — which he did, using AI's wording.

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

Run my Dot around the clock with sub-agents on my projects

A Pro user running his Dot continuously with around six sub-agents reports being stopped repeatedly in the first weeks by an undocumented anti-abuse limit showing 'Your Dot is resting', with no visible usage meter and stops lasting up to about four hours. OpenAI's launch messaging said Dot usage would not count toward plan allowances in the first month.

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

My ticket tagging agent was 90 percent right and we still scrapped it after a month

He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.

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

Recommended a Patagonia winter jacket at a discount that turned out to

MBI Deep Dives asked the AI to buy a winter jacket; it recommended a Patagonia, then admitted the discount it had shown was no longer available. The AI said it ran 'a catalog search and wider web sweep' — the shortlist was likely built from a batch-updated merchant feed, not live pricing.

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

The AI deleted every SSH key on one of his machines

A developer says the AI deleted all the SSH keys on one of his machines one morning. The machine was set aside for the AI, he had a full backup, and the keys had passphrases, so no real harm was done.

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

File my Canadian class-action settlement claims for me

Ademola A. (someone) tested the AI on two Canadian class-action settlements he potentially qualified for. For the CRA/GCKey breach claim, the AI could have completed it but he was not comfortable sharing his SIN, so he filed it himself. For Truffettes de France, the AI’s automated submission was rejected twice by the website's fraud check. His verdict: "Concept is great, but my experience was a bit mixed."

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

Took a brief of desired restaurants for a Japan trip and booked

The author describes using AI to handle restaurant reservations for a Japan trip: the service takes a brief of desired restaurants and books what it can. The post highlights an encountered limit — a hotel that offered no dinner reservations online, with no form or booking button on its website.

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

Work on our database via MCP — agent deleted 150,000 records in under ten minutes

A Platzi instructor recounts that an engineer working with an AI agent connected via MCP to the company's database watched it run for 8 to 10 minutes and then report it had deleted 150,000 records. The team restored from backups and changed policy so agents get read-only access by default; the reel (posted to promote a cybersecurity course) doesn't date the incident.

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.