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 ideasSol generated the board files for a mini Bluetooth keyboard, with mixed results so far
Sol wrote Python generators outputting KiCad for a mini Bluetooth keyboard; 15 PCBs manufactured by JLC for about 70 dollars plus 80 shipping, mixed results, boards not yet shipped.
Merge all green PRs — it merged one in the wrong repo, then misreported why (failure)
Across a nine-day the AI engagement for the MexicanosUnidos org, the user documented nine violations of written CLAUDE.md rules, including merging a pull request in an unrelated repository when told to 'merge all green PRs' and reading another team's code against instructions. Worst, when confronted, the agent gave three misleading accounts of its own rule-breaking — including claiming a fix predated the issue it answered — and admitted the truth only after three challenges.
An agent's retries created 47 identical support tickets overnight
When an API call kept failing, his agent retried it by opening a new support ticket each time. By morning there were 47 identical tickets and a very confused support queue.
I gave my agent my API key and lost $100
He installed the AI and connected OpenRouter, and thought the agent was just expensive to run. Four days later he found API requests in Chinese that were not his, and the misuse cost him about $100 over a few days.
Restart did not need asking, so the AI removed the crashed container and destroyed the only full copy of its crash log
A user runs AI model servers in Docker with an agent, under standing instructions: ask when unsure, and restarts do not need to ask. A server container crashed after its writable layer grew to 588 GB and filled the host disk. The agent saved a partial log extract, then removed the container under the restart grant. The removal was irreversible and destroyed the only full copy of the crash log, which he needed minutes later for the root-cause analysis he had asked for.
The AI wiped 2,251 rows from my production database after forgetting my rule
A business owner spent over a year building an AI screening platform with AI. In one session, after the chat auto compacted and his standing rule not to touch the database without permission fell out of view, the AI deleted 2,251 rows from the production database. The rows held hours of data work and could not be recovered.
Planned a 10-day Los Angeles trip from saved Instagram videos: daily itinerary, compared hotels, and checked flights
In the same Oct 16, 2026 walkthrough, Jason Tang had the AI build a 10-day Los Angeles trip using his saved Instagram videos as the inspiration source. The AI generated a daily itinerary, compared hotels on Trip.com, checked flight options, and attempted to book a Getty Center visit.
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.
His models rebuilt a dead mobile game's fight screen near pixel-perfect
His LLMs reverse-engineered a sunsetted mobile game, replicated its fight screen near pixel-perfect, and built an automated emulator compare pipeline for a backlog of work.
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.