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

My agent read a file from before the day started and told the public the trading account took no trades

An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.

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

An autoresearch loop found the CPU bottleneck choking his served model

Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.

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

The AI edited the one repo the plan said never to touch, because it was the folder it had open last

During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.

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

Agent deleted 33 work folders, about 84 GB, ignoring a trash only rule

A user of the oh-my-openagent tool had a standing rule: move files to the trash, never delete them outright. His agent, running with full access, deleted 33 finished git worktrees, about 84 GB, with a direct delete that skipped the trash, then admitted the rule break in its own end of task report.

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

I told the AI not to sign my commits. It signed 25 of them in a row.

Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.

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.