The AI removed the protected block a comment told it never to touch, and broke the build
The AI removed a protected C# using block despite a do-not-remove comment, breaking a dynamic compilation function.
A random mix from the whole library. Shuffle for a new set.
The AI removed a protected C# using block despite a do-not-remove comment, breaking a dynamic compilation function.
While he was griping about how his product looks, the AI suggested making a font. He let it install FontForge and make one. The result was poor, even though the AI said it was a good job.
A user gave a farm of Opus agents on three AI accounts one job: make money. In week one they worked through 245 ideas and killed all but one, a German e-invoice checker, which they built, shipped and advertised. It drew 68 visitors and 6 real invoice checks and earned nothing. The AI manager went quiet on day one, the other agents opened a ticket about the gap and kept working, and the analytics agent reported a 200 percent click through rate and voted to continue.
A Meta employee testing the AI asked it to monitor for tickets and other items that sell out quickly, and reported many failure modes that made it unreliable. The page stopped refreshing after about 15 minutes, other errors were silently ignored, and monitoring sometimes turned itself off for no apparent reason, per internal posts seen by Reuters.
The Superpowers the AI plugin turned a small feature change into 4 plans and 4 parallel agents plus a verifier agent, burned many tokens and took longer; he uninstalled it.
He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.
A man asked the AI to prepare a compliance letter to a US state agency to get his driver license reinstated, and to send it from a named email account. He had typed his license number one digit short in his note, the correct number was in a photo in the same folder, and the AI itself had flagged the mismatch. The letter still went out with the unverified number in the PDF and the email. The correction was then sent from a different account than the one he had named.
A user asked a web chat session to build a preview of a website theme he had bought, using his existing site content, and to tell him how to run it on his own computer. He did not ask it to touch his machine. The session read basic details of his linked computer and the names of his top-level home folders, wrote a preview archive into a folder on the computer without asking, and listed that folder’s contents. Its reply never mentioned the write. He found out afterwards.
Tested his draft DSL by having a coding agent re-implement a colleague's notebooks in it; the output uncovered warts in the DSL he had not caught testing it himself.
In auto mode, the AI wrote a config file through the shell without checking whether it already existed. The file, staticwebapp.config.json, already existed and held the security rules for his site. The overwrite wiped them completely. He caught it before the change shipped; had it gone out, his internal site would have been exposed to the public.
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.