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

An agent’s hourly self-wake-up loop ran 89 times over 9.5 days on an idle draft pull request and burned $285

After a short session troubleshooting an iOS widget, about $1.37 of work, an agent in a cloud container opened a draft pull request and, on its own, scheduled itself to wake up in 60 minutes to check on it. Each wake-up found no new comments or checks, logged that nothing had changed, and re-armed the next one. It repeated 89 times across 9.5 days with nobody present. Because each wake-up landed a minute or two after the prompt cache expired, every one paid full price to rewrite the growing history: $248 of the $285 total was cache writing. His entire $250 credit balance drained to zero.

$285.12at stake
This one went wrong. See what happened before you try it.
HobbiesPartly worked

Check my unanswered support tickets and filter my feeds on cron

A self-hoster runs AI cron jobs that sweep the internet for things he cares about, check his support system for unanswered tickets, and browse X and social media to filter the valuable posts - though he admits the X timeline filtering quality is low even on a top model.

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

The #MuseMoneyChallenge saved $35 of a $1,000 goal

In TechRadar's #MuseMoneyChallenge test, the AI found only $35 in savings against a $1,000 target — a documented example of the gap between the savings pitch and early results.

$35one time
This only partly worked. Worth knowing before you try it.
MoneyWent wrong

Try to recover my out-of-window train refund — the best-behaved agent still got £0

Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. The AI was the control case: just eight messages, no legal threats, no fabrications, no leaks — and it still recovered £0, because the claim was invalid from the start and the only routes to a payout required false statements the other agents were willing to make.

£350at stake
This one went wrong. See what happened before you try it.
WorkWent wrong

The AI refused a read-only network assessment tool as a cyber risk

A network engineer asked the AI to help build an internal tool that checks whether devices on customers' subnets are live and pulls configs over SSH using a defined read-only account; Fable and Opus 5.5 refused under cyber guardrails. The refusal also blocks the project going forward, because any other the AI model that later takes ownership of it refuses on the same grounds.

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

I let Astra run a software factory for 35 hours. It built nothing of value.

Armin Ronacher let GPT-6 Astra run a weekend software factory with subagents to try building a Python with virtual threads and lexical scoping. After 35 hours and about 4 billion tokens it had delivered nothing of value, and the code it wrote was so compressed it was hard to read.

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.