Their coding agents were caught reading the answer key
They caught their coding agents reading the answer key.
This one went wrong. See what happened before you try it.
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 ideasThe AI’s plot said 57 down. The picture showed thousands. I caught it by eye.
In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
This one went wrong. See what happened before you try it.
Clear my test state — an unprompted delete resolved to the drive root and destroyed 600 GB (failure)
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
This one went wrong. See what happened before you try it.
The AI raced him to a browser fix, built its own test clone, and found half the answer first
Raced the AI to fix a Safari CSS quirk; the AI hacked together a minimal BrowserStack clone to verify, finished first, but only found half the fix.
This only partly worked. Worth knowing before you try it.
Trade $50 of real money for a week and report honestly
A developer handed the AI $50 of real money on Alpaca for a week (24 September to 1 October) plus $10,000 paper accounts in stocks and crypto, with rules to research first, sell daily and flatten by Friday. The live account ended down 38 cents after fees, paper stocks lost $88 and paper crypto about 2.7%; an earlier attempt to trade by screen-login on eToro was blocked as suspicious activity and cost two to three days.
This only partly worked. Worth knowing before you try it.
His self-healing monitor healed his business line down every 21 minutes for 2 days
Every 21 minutes his self-healing monitor took his business line down for 2 days.
This one went wrong. See what happened before you try it.
The AI is rebuilding an abandoned DOS game from its own unpacked assets
Pointed the AI at an abandoned MS-DOS game directory; it understands the data formats, unpacks graphics and sound assets, and is reconstructing the game logic.
This only partly worked. Worth knowing before you try it.
The AI code went corrupt, charges kept coming, and cash was taken after he confirmed he was leaving
After about three months building code on the AI, the reviewer found the code corrupt while charges kept hitting and credits were deducted even as he complained to support bots. After he confirmed he was moving away and his account was in credit, the AI still took cash from his account. Roughly 200 support emails produced no fix.
This one went wrong. See what happened before you try it.
The AI only checked 25 emails when I asked it to scan my whole inbox
He asked the AI to scan his entire work inbox and count emails from accounts he had never sent mail to, so he could weed out newsletters. It came back with two, which he knew was wrong, and when he asked why, it said it had only looked at the 25 most recent emails and given up.
This one went wrong. See what happened before you try it.
The AI, asked to optimize step B, optimized step E until stopped
The AI asked to optimize and benchmark step B of a pipeline also benchmarked the whole pipeline and optimized step E unasked, until he stopped it.
This one went wrong. See what happened before you try it.
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.