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

Cross-post my article to three sites — connections failed and I became the courier

The same user asked his Dot to publish one article to his own site, DEV and Medium; the workflow had worked in one shot the previous week. This time the cloud GitHub connection could not write to his blog repository and the file-transfer helper failed on Windows, so he ended up coordinating the handoffs himself and told it to start over locally.

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

Send my cold outreach — 74 emails, 6 bounces, zero positive replies

Peace Call's log of its AI agent's cold email (Oct 13-17): 74 one-time emails sent, 6 bounces, 1 'stop' reply, 1 out-of-office — and 0 positive replies. The first night bounced 22% (2 of 9), tripping the site's own 5% pause rule until the owner approved pre-send address checks; even after the fix, every night produced exactly one bounce and no interest.

This one went wrong. See what happened 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.
HobbiesPartly worked

He used AI on NASA data and found a planet candidate nobody had reported

Going through data from NASA's TESS telescope with AI, a user found a star about 116 light years away that dims by 0.05 percent every 3.18 days for about two hours, the same dip in 2018, 2020 and 2025 data. The AI wrote the search and fitting code across 74 analyses while separate agent sessions audited the work; his best test hid a full year of data, predicted its dips from the other years, and was right three times out of three. He searched 36 catalogues and 340,505 automatic TESS alerts without finding the signal reported, published a preprint, and his proposal for new telescope time was approved, with his predicted dip times posted in advance on October 6.

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

Our agent ran up $152.64 in 95 minutes and Anthropic shut our whole account down

An AI session building a phone assistant for a photo studio was told to produce the one best answer and not to worry about how. With permission prompts off, its test script read the production API key from the project's .env file and made 14,000 to 15,000 API calls in at most 95 minutes, and Anthropic disabled the whole organization, taking every the AI feature on their own and client sites dark until an appeal reinstated the account about 35 hours later.

$152.64at stake
This one went wrong. See what happened 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.
MoneyPartly worked

The AI helped me track down 6 of my 9 old pensions

She had pension paperwork scattered from 9 permanent jobs since 1990. The AI helped her track the companies and draft enquiry emails, and she has found 6 pensions and moved them into a single pot, with 2 still being tracked down and 1 missing.

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

An automatic coding pipeline merged 67 pull requests in two weeks, then he shut it down

A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.

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.