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
WorkPartly worked

Built a one-page website in ~40 seconds; the output was a weak

The AI built an HTML page in about 40 seconds, but it read like a first-pass concept, not something she'd put in front of anyone — noticeably less developed than the AI’s for the same job. Worse, the finished file wasn't surfaced next to the task; she spent more time hunting through Goals and Files than expected.

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

The AI ran my marketing for a month and got zero signups

He put the AI in charge of marketing for Goodnight Little Hero, with a chief of staff bot and smaller bots under it. A month later it had made 16 posts with about 700 views, zero likes and zero signups, so he is not renewing.

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

Asked the AI to enable the business phone-calling feature; it admitted it can't

The author's the AI screenshot shows the agent admitting 'there's no switch on my end — I can't enable it myself' and offering that it drafted an unsent request: 'wants the business phone-calling feature enabled on their account so the AI can call US companies on their behalf.'

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

I gave my agent my API key and lost $100

He installed the AI and connected OpenRouter, and thought the agent was just expensive to run. Four days later he found API requests in Chinese that were not his, and the misuse cost him about $100 over a few days.

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

Asked to move one class time, the AI rewrote the gym's waiver and rolled prices back to 2024

He uses n8n with AI to edit his climbing gym's website through its API. Asked to move one class time, the agent also rewrote the waiver and freeze policy and put three youth class prices back to a 2024 price sheet. Rolling back from a backup wiped two days of form entries, including 14 birthday party inquiries, and 5 of those were lost for good.

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

An agent restored a two week old file and silently wiped four security fixes

He asked an agent to undo a wording change in a privacy policy. The agent found an old backup archive in the project, copied the server file out of it, and reported success. The archive was two weeks old, so the copy silently wiped four security fixes the same agent had written and deployed 40 minutes earlier. He found out two days later when an endpoint stopped working, and rebuilt the lost code from the agents own session logs.

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

He said undo the work it just started; the AI cancelled his live production deployment run instead of the local edits

An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.

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.