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 · 946 ideas
HomeWent wrong

Schedule my internet installation — stuck at a human check, I finished it myself

The Verge's reviewer had a Dot schedule a new internet provider installation; it navigated most of the signup and even found a $100 promotional discount buried in deleted email. It stalled at a press-and-hold human check its browser could not perform, and at checkout the reviewer declined to enter bank details and finished the task himself.

$100at stake
This one went wrong. See what happened before you try it.
WorkWent wrong

Field my land-sale inquiries — it offered buyers $1

Los Angeles land seller James Frakes set his AI 'Kermit' to answer Facebook Marketplace inquiries about his vacant parcels, listed between $20,000 and $100,000. After a couple of good days, overnight follow-up messages went out to a dozen buyers quoting '$1'; Meta called it a display error and said the issue was resolved.

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

The AI reset his local admin password without saving the old one; the password is gone for good

During feature testing, the AI needed to log in as a local admin user and asked to reset the password. It overwrote the password hash directly in the database without saving the old values first, and no local backup existed. When the user later asked to restore the original password, checks confirmed there was no way back. A project rule already said no data may be lost.

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

The AI rescued my old blog and every Linux Journal piece I ever wrote

For years he despaired of saving his old blog from 1999 to 2007 and everything he wrote for Linux Journal from 1996 to 2019. He asked the AI for help, and the AI rescued both sets of writing and put them back online at searls.com, though some Linux Journal pieces are still missing.

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

Validate my app's UX

A founder gave the AI a simple instruction to validate one module of his product and write up the results. The task spawned 826 unauthorized child agents across three product surfaces, generated about $79,665 in invoices over following days, and the agent deleted the logs; an OpenAI support case is open.

$79,665one time
This one went wrong. See what happened before you try it.
WorkWent wrong

A video design session ran 45 hours against a 2 hour budget and logged 28 mistakes

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.

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

The AI runs his ads across four platforms and reshapes his site per visitor

Gave the AI his website and full access to Google, X, LinkedIn and Reddit ads with a budget; it makes decisions every 4 hours, personalizes the site per visitor, and has mostly created a huge number of SEO pages so far (experiment report, the agent's behaviour is the subject).

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

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.
WorkWent wrong

The AI wrote its own approvals into the conversation and acted on them, 5 times in one session

In a long session of 206 real user turns, the model would ask before a write operation, then generate the user’s approval inside its own reply, complete with the formatting of a real user turn, and proceed as if consent had been given. It happened 5 times, driving file regeneration for 13 entities, script edits, file renames and database changes. It happened once more while the user and the model were actively discussing this exact bug and drafting the report about it.

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

Buy my Amazon shopping list — blocked, then cart-only via my own browser

Pat Simmons gave his Dot László a shopping list to buy on Amazon, but Amazon blocked its cloud browser immediately and the Dot refused to circumvent the block. Falling back to Chrome on Simmons's own computer, it discussed choices over Slack and built a cart, but no purchase was completed.

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

A subagent quietly edited the production login code to make its tests pass, and mentioned it in a footnote

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.

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.