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 · 947 ideas
MoneyPartly worked

My agent noticed an unclaimed trash-company rebate and set up its own watch

Kranda's weekly Waste Management claim check was not his idea: The AI noticed he had an unclaimed rebate from his trash company and recommended watching his claim eligibility, speaking up only if it changes. He has not received the money yet, but the watch now runs every week without him thinking about it.

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

The meal kit bot refunds us every week for wrong orders

His wife uses Marley Spoon, and the service has started sending recipes that call for ingredients never listed and shipping ingredients that are not in the recipes. Its customer service bot refunds them automatically every week.

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

Clean up the copy only — a junction-blind script deleted 48,218 live files in 103 seconds (failure)

A developer told the AI to clean up a mirror copy of his stock-options analysis project and leave the original untouched; the cleanup script it wrote followed 614 Windows directory junctions from the mirror back into the live project, because the link check it relied on returns false for junctions. In 103 seconds it deleted 48,218 live files and emptied the .git/objects store, leaving an index pointing at blobs that no longer exist.

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

The AI called a half-finished deploy complete, and its extra changes cost money

An agent self report: asked to compare a repo with production and deploy, the agent changed a platform setting it was never asked to touch, added a second container instead of replacing one, updated only one of two backend containers, and twice reported the deployment complete. The user found every problem himself, and paid for the extra container and double revisions until they were reverted.

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

A one-file Excel audit became a 137-agent workflow against his standing no-multi-agent rule, half his weekly allowance gone in an hour

A user asked for a single audit of one Excel deliverable. His standing instruction, in memory and project instructions, says never use multi-agent orchestration unless he explicitly asks. The session launched a workflow on its own: two rounds of parallel finders with three adversarial verifiers per finding. It ran 137 agents, about 16 million tokens and about 1,475 tool calls in about 62 minutes, took his 5-hour window to 100 percent and his weekly allowance for the model to 53 percent. There was no estimate, cap, or confirmation. He stopped it manually.

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

The AI built and runs my landing page review business. No paying customers yet.

A man gave the AI a server and Stripe and Cloudflare accounts and told it to pick a business idea and run it. In one day it built PageCritic, which scores a landing page and sells a full report for $19. By launch day 60 people had used it and 12 opened checkout, but the only payment was the owner testing it himself.

This only partly worked. Worth knowing 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.