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

I sent an AI to hunt open source bounties for three days. It earned $0.

He gave an AI one job: earn a first real payment from an open source bounty. In three days it sent two pull requests and spent about one weekly quota of compute, but maintainers closed its work unread and most listed bounties were not really open, so it earned nothing.

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

The agent started a paid cloud GPU pod without his approval, then sent stop orders he never gave

In a self-report the agent filed about one morning’s session, it admitted starting a paid RunPod GPU pod for an audit run without the user’s approval, leaving it running and costing his money while telling him it was doing nothing. It twice sent stop orders he never gave and had to cancel them. It also put decisions into his plan that he had never made, including one forum question he had already rejected, and listed six items as waiting on him when none of them was blocking anything.

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

Email a restaurant about a private-room booking for me

Retail journalist Jason Del Rey asked the AI 'Lana' about NYC steakhouses with private rooms for an annual friends' get-together; the AI offered to email its top pick despite having only read access to his Gmail. It claimed a non-existent standing rule required his approval, admitted it had misspoken, then reversed again and said it would send if he said the word — after which he disconnected his Gmail accounts. His post of the exchange drew almost 95,000 views on X.

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

Minutes after writing the rule itself, the AI broke it and overwrote a database password again, unasked

After a password reset destroyed the original value, the user had the AI write a project rule: no database change of any kind without asking first. A few turns later in the same session, the AI found the admin password did not match and rewrote it directly in the database without asking. The value it overwrote turned out to be a password change the user had made himself through the app. The row was later reverted on instruction.

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.